New! Inserting Jira issues into Confluence pages is easier than ever ✨

[#1]

Hi Atlassian Community,

I’m David Michelson, a product manager on Confluence Cloud. We've been working on an exciting update to modernize the experience of inserting Jira issues into Confluence--making keeping your team in sync about work in Jira easier than ever. Introducing, Jira Issues (/Jira Issues)! We are gradually rolling out the feature, so you may not see it in your instance yet.

Using what we’ve learned from how customers use our previous solution, the Jira Issues Macro (formerly /Jira, now /Jira Legacy), we’ve made it easier than ever to insert and view Jira issues in Confluence using our new element, Jira Issues (/Jira Issues), thanks to the following improvements:

• ✍️ JQL suggestions, syntax highlighting, and error highlighting

• 🤌 Drag-and-drop field re-ordering & a simple dropdown to add or remove fields

• 🎨 Modernized and simplified visual design

• ♾️ Infinite scroll through Jira issues

• 👆 Powerful hover preview for Jira issues 

• 🔎 Support for basic keyword search

To get started with Jira Issues, when editing a Confluence page:

Select the + menu in the toolbar, search for "Jira," and pick “Jira Issues”

Or, just type "/jira" directly in the editor and pick “Jira Issues”

Then, make a search for the issues you’d like to insert either with JQL (learn more about JQL) or basic keyword search. For example, you may want to grab all the issues assigned to your team that have not yet been resolved so you can report on your team's progress in Confluence.

If you are a member of multiple Jira sites, use the site selector at the top to pick the issues from the site you choose.

Once you have the issues you’re looking for, you can add or remove the fields/columns you want to display by clicking the column selector in the top right of the issue table. Then, you can drag-and-drop to re-order them if you like by simply clicking and holding the top of a column and dragging to a desired location.

If you’d like to insert issues as a simple count view smart link, select “COUNT VIEW” in the top corner.

Hit “Insert issues” and you’re done!

If you need to make any updates to your search query, simply click on the table or count link you inserted while editing and hit the pencil icon found in the toolbar at the bottom.

Now that you've inserted Jira Issues, try hovering over an issue key or summary! Notice the helpful preview where you can quickly copy the issue link, open a preview, and even update the status, right from Confluence 🤩

For an even simpler insertion experience, you can also just paste the URL of any Jira issue search or filter into the page, and it will automatically display as a Jira Issues table.

• Just like the other methods, you can add or remove fields you want to display, and drag-and-drop to re-order them if you like.

• If you need to make any updates to your search query, or whether you want it to show up as a table or count view, simply click on the table while editing and hit the pencil icon.

• If you’d like to show a basic blue link instead, just hit undo after pasting.

FAQ

How can I give feedback about Jira Issues?
Leave a comment right on this post! We are planning improvements to Jira Issues (for example, adding simple dropdown filters to basic search for fields like Project, Status, Assignee, and Type) and would love to hear from you.

Why am I not seeing Jira Issues in my instance yet?
Since we are gradually rolling out Jira Issues to customer instances, you may not see Jira Issues just yet, but you should in the near future.

Does Jira Issues work with Jira Server issues?
Jira Issues will not support Jira Server issues. Jira Server customers will still be able to use the Jira Issues Macro, which supports Jira Server issues, via /Jira Legacy

Can I use Jira Issues to display Jira information within vendor macros or Confluence macros like the Page Properties Report?
Jira Issues will not initially support vendor macros and some Confluence macros like the Page Properties Report (it will appear as a link to those macros). In the meantime, customers can still use the Jira Issues Macro, which supports vendor macros and Confluence macros like the Page Properties Report, via /Jira Legacy

[Dave Mathijs]

Why are the colors of the status lozenges not corresponding to the status category (i.e. grey for to do, blue for in progress and green for done)?

To Do is pink/purple and Closed is red? Very confusing.

[Nikki Zavadska _Appfire_]

Oh wow! This looks great, I'll try it for my status update docs 🔥

[Debbie Jolley]

@Dave Mathijs agree with you re the confusion. 
It seems there's some inconsistency in the screenshots they've used in the article

[Dave Mathijs]

@Debbie Jolley It's not only in the screenshots used, it's an effective issue in the app.

[Dan Tombs]

Minus the status lozenge colours not matching as @Dave Mathijs correctly pointed out (think this is a genuine concern as users who are scanning are not going to see things in a way they are used to and is standard in every other aspect), this is really good to see improvements to the Jira macros. It is much needed and finally great to see improvements between the two applications.

[JG Meillaud _]

Hi,

This looks great at first glance!

Conversion from legacy needed?

A legacy editor is mentionned in the article. Will we have to convert the macro to the new Jira issue macro or will this be automatic?

I agree with the others about the colours

Inconsistent colours are confusing, however it would be great to be able to manually associate statuses to custom colours in the macro itself.

Cheers,
JG

[Summer_Hogan]

Thanks @David Michelson - I'll have to test some of these new features out! 

[Paulius Jankevicius]

It looks nice but it has a serious bug: it does not work when there is 1 item in the results. This bug is causing a big trouble in our work flows. It puts a regular link of one item in this case, and only puts this nice table if there are 2+ items.

Is this going to be fixed?

[James Crossman]

This doesn't seem to work when exporting to PDF.

All I get is a hyperlinked address to Jira - which makes the export to PDF completely useless for my purposes.

[Rino Moen]

👎
I have a whole setup with the old 'Edit Jira Issues/Filter'

Please make the old version an option to use, I don't want a scroll box on my page.
Also add option to edit how many issues are displayed at once, this box is so slim I can only view 13 issues at once

Also clicking the column header doesn't sort.

It does have it's charm and is useful but it seems like this needs more work and user testing, looks more modern but doesn't work as one would expect on all aspects

Adjusting the columns is also a nightmare, what logic is used here? I move one column border and all of them shift

Edit: I see now the legacy option is available

[Priya_Perera]

New feature looks great, but it has brought back the word-wrap issue. Blast to the past : https://jira.atlassian.com/browse/CONFSERVER-28378

It would be fantastic once this is fixed. :)

[Kim Bartolome]

This feature is fantastic!

I am trying to expose the Project Board Name but am unable to successfully pull the information from the standard Jira field name 'project'. Is this a known limitation if my query spans across a project category?

[Jörg Hoffmann]

Didn't have a chance to try yet:

Does this macro refresh automatically based on the filter like a Jira dashboard or is it just static and the JQL query is only used once to get the issues you want to insert?

[oren_david]

Long text is truncated. Sometimes it's required to see the full text.

[Patrick Russell]

Display on larger screens seems to not work when in viewer mode:

However, when editing the same, I can manipulate the column width and have the expected rendering:

[frederic]

Looks like a great improvement! Just tried it and it works great. Autocomplete in the JQL query would be a nice delighter. But already very happy with this!