Update on the Jira Legacy Macro conversion — We Hear You

[#1]

Hi Community,

This is Laura from the Confluence product team. We know many of you have run into unexpected issues since the migration of the Jira Legacy macro to the new Jira Work Item macro (originally announced here), and we want to address your feedback directly.

This migration caused more disruption than we anticipated, and we didn't adequately prepare you for it. We recognize that some of you are experiencing real workflow gaps. There are some features you relied on that aren't yet fully at parity in the new macro. That's on us, we’re sorry.

Known issues we're actively fixing

We've heard your feedback and are urgently prioritizing fixes for the following:

• Inability to sort by column in the Jira Work Items macro (JAC ticket)

• Column width settings not being carried over from the Jira Legacy macro (JAC ticket)

• Jira Work Items not rendering when nested inside a list on a Confluence page (JAC ticket)

We are treating these issues as high priority and aim to address them in the coming weeks.

If you are experiencing any business critical issues please contact Atlassian Support and reference this post.

Why we made this change

The Jira Legacy macro has been a significant source of performance and latency issues in Confluence, and modernizing this integration is critical for the long-term health of the platform. That said, we should have done a better job communicating the gaps upfront and making sure there were no critical gaps before rolling out. We're taking these lessons seriously and will do better on future rollouts.

Thank you for your patience and for holding us accountable. We don't take your frustration lightly.

-The Confluence Team

[Stephen Pilkington]

Can you also address:

• Dragging of columns to reorder them not working consistently; often it highlight one column but actually drags another
• If the Edit button is at the bottom, selecting it should not be a drop-down; else users can have to perform an extra scroll just to see the options. It is also inconsistent with the ... menu next to it, which displays the options above or below depending on the position on the screen. It took <30 s of usage to spot this poor UI design.
• Wrap text in Summary and Description as default
• Give the option to display the whole list, or a summary

In the meantime we are replacing the new macro with the legacy one on dozens of pages. 

[Bernhard G_]

In addition to @Stephen Pilkington 

• Wrap text basically for all columns by default. I guess most users will prefer that anyway instead of cut text and so it will be less work if you just have to disable it for some special cases. Find a solution to set it via bulk change for all updated macros, otherwise it will cause hours and days of work to reconfigure dozens of pages.
• Don't add the key-column by default if it was not visible in the legacy macro. It had a reason why it was not visible and has to be removed on dozens of pages now. Therefore find a solution to undo that by bulk-change, otherwise it will also cause hours and days of work to reconfigure dozens of pages.
• If pictures are used in multiline textfield columns, they get cutted -> Adjust the size of the images to the column width or add at least a horizontal scrollbar.
• Give the viewer the option to sort by column or even as a new feature to filter.

[Harald Lurger]

The order of the columns DOES NOT stay the same.

Before: "Key" | "Release Notes" (custom field)
After: "Release Notes" (custom field) | "Key"

If I edit the page and click "Configure colums" it I see the "Key" column twice:  Key, Release Notes, Key
BUT, only the second Key column acutally contains the Jira Keys
 

[Kent Chiu]

Unable to set column settings when the query does not return a result, hence there is no way to set up the column to display.  Column setting should always be available to set. The query can have different query results at different times.