When inserting Jira issues in Confluence, could it be possible to display the Confluence pages linked to the inserted Jira issues as well ?
If I am not mistaken, we can add a column displaying the linked issues. I would like the linked Confluence pages as well. This would really be a game changer for us.
Hi @David Michelson I have made pages for our external customers and the links not working. It's working inside our company, but not for external users, so should we give rights for the customer to use Jira or what can be the problem?
It's a pity that this change was not part of a bundled track. We discovered it recently only while trying to use the "legacy" /jira macro...
By the way, this change is very confusing for our users since we used to manage lot of tables with /jira legacy macro. Is there any plan to deprecate this legacy macro at one point in time? If yes, what will be the behaviour for all pages already containing the /jira legacy macro?
Otherwise, we found that tables generated with this new /jira issues macro are not correctly exported in PDF or Word documents, whether using the standard "Export to PDF/Word" or when using our "Scroll PDF Exporter" plugin. This is really a concern for us, especially when these tables are embedded in Confluence pages used as regulatory records. Do you know if there are any plans to resolve this export issue?
We just migrated to the cloud and we have several statuses...if there was a way to 1) format the color of the status lozenge, that would be great. Right now we have two statuses with the same color. 2) would be great if we could format the date timestamp. We just need the date.
to this new Jira Issues macro. In the Jira legacy, we can set how many results we want to display by default, this settings seems not available in the new Jira Issues macro.
the re-size to the max width seems not to work properly. We can see here that the expand is more on the left than the Jira issues filter that is just below Here in page edit mode we see that I cannot put more width to it
Question
Is it in the future features pipeline to be able to use "Insert Chart" table feature with this new Jira Issues macro?
Hi, this is great. Just one question, I created filter for all service management issues, but the table does not show the Project. The column is totally empty. We have several customer service portals. Is this a bug or just one of the Jira oddities?
This is a good macro inline or in the UI and I was very happy to see the text in the tables is larger and legible when you export to PDF, however looking closer at the PDF for me there are 3 issues:
The table only shows the first 10 issues in the list and there doesn't seem to be way to change this so you can see the full list in the PDF version. The legacy macro shows 10 per view in the UI that you can page through and in the PDF version the full list is printed.
There is no word wrap in the table lines - this is both in the UI and PDF as mentioned above
The table cuts off columns in the PDF even if it only has a few.
When you want to include a Jira issue's description field, you can set the 'Wrap text' option on the field by clicking on the 'Description' header. However, you only get the first two lines of the Jira's description, and they don't retain their newline between them. Any thoughts on this?
I tried continuing to use the Jira Legacy Issue macro, but when I include the description field in that, any inline images in the description get blown up to a very large size that makes the overall Confluence page unreadable.
The reason for including the description field, in my case, is that I want to show the detail of the story (issue ticket) in Confluence as documentation of a feature.
AFAIK This is only available to bring issues from Jira Cloud.
We get issues on report pages from both Jira Cloud and Server Instances. The legacy macro was available before so we could use them in junction. But now I see the legacy macro's UI has been updated and unfortunately it's unusable. Selecting columns from a loooong list and any wrong click deletes the whole list. It needed some update but definitely not this one.... Is it possible to use the old version somehow?
Understanding that the Legacy editor in Confluence is being decommissioned (no date received from Atlassian as yet). I am trying to replicate Jira reports in Confluence new editor and I have seen challenges:
The settings in the legacy editor are not supported in the new editor.
Using the Table Transformer in the Table Toolbox to merge and transform two Jira tables. The SQL does not read the columns being returned by by T1 and T2.
Work around.
Using the Table Toolbox Jira filter T1 is nested inside a Table excerpt and Jira filter T2 is nested inside a second Table excerpt.
The two excepts are then lifted by Table Excerpt include (not part of the Table Toolbox) and included into the Table Transformer in the Table Toolbox to then allow for the merger and transformation.
Are there any plans of any improvement as I am currently facing a weeks additional work load to rewrite multiple pages.
Correction
Upon further testing I do not need to use the excepts. However, I do have a challenge when I have Jira filters returning a lot of rows that it becomes a challenge inside the Table Transformer to move from one Jira filter to the other.
In the legacy we do not see the full list but just an image.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
We are a little bit confused by your description and ask you to refer to our support where you'll be able to share your screenshots for a better guidance.
Meanwhile, let me explain that the Table Toolbox macro is a special shell to nest different macros like you do it in the Legacy editor.
You don't need any Table Excerpt/Table Excerpt Include macros to reuse you Jira macros: you just insert the Table Toolbox macro, place your mouse cursor inside its body and insert one or several Jira Issues macros on the page. Your Jira macros are wrapped in the Table Toolbox macro.
Then you open the Table Toolbox macro settings and on the left panel you'll see your Jira tables and a bunch of our macros that you can easily arrange in various combinations. For example, wrap all your Jira tables in the Table Transformer macro and then place the Table Filter macro on top.
For example, on the screenshot below I have a manually created table subsequently wrapped in the Pivot Table and Chart from Table macros:
The configuration for the number of rows to display is still not available. For me the new Jira Issues macro always displays all records, and I have over 30 that take a lot of space on the page. I just want to display the first 10 rows.
This is the biggest feature missing from my perspective and the top priority to fix.
Our primary use case for the linkage of JIRA issues within a Confluence document is for the production of Release Notes. For obvious reasons we want Release notes to reflect the version of the release at the time the release notes are generated. This means we either output them to PDF or Word. Neither outputs work. This means that the ability to 'freeze' a confluence page is now gone, so Confluence cannot be used to record validation documentation.
That said, with the lack of wrapping support, this is an improvement. The manifestation in export is required in order for it to be useful as a replacement for the legacy macro.
Hi, @David Michelson it seems there's a problem with the toolbar at the bottom of the Jira Issues panel. I can't edit the component anymore. The pencil button is missing. Thanks for your answer,
This is great! But... is there any way to do it from the draft page, instead of the published one?
We really want to allow readers to insert jira tickets on the draft (so they can request changes or updates to the page) without the issue link appearing on the published page.
This seems nice, but in Cloud Jira/Confluence I'm using, there is no way to edit this new Jira issues table once it is placed on the page. There is no pencil (edit) button to click on.
My primary use-case is inserting a link to one specific issue as an inline link when doing minutes.
Thus I provide the issue-key as input, but more than often I get 2+ results?! See attachment for an example (i left it on "list" to better visualize the problem), where I input MGR-1115, but get MGR-1115 and MGR-1113 as results. In this case, I can't even filter to force the result to the expected singleton.
Also the default is always List. I would prefer a setting somewhere allowing me to have Inline Link as default.
I can revert to the legacy option which does not have this problem!
Put your meeting notes on autopilot with Loom + Confluence
AI-powered meeting notes keep work moving even if you’re out of the office. Enjoy your well-deserved time off and return refreshed, confident you’ll catch up in no time.
57 comments