Using Jira Issues Macro is the great experience indeed but what if it is not supported on Scroll Viewport? It does not have much value if we can't share this experience with our customers. What does Atlassian recommend? How should we create an offline Jira report to be published for public release?
This is a great improvement. Is there any thought about allowing updates to be made to the Jira issues directly from Confluence? Use Case: we have a team that likes to use a filter to currate issues to review during a meeting. It's quick and repeatable while minimizing manual effort to copy from Jira, paste into Confluence page. They'd greatly appreciate the ability to simply click in the column for the field they need to update during the meetings rather than having to open the ticket in Jira to make the update. In our use case, we have custom fields that need to be updated.
I've opened a support ticket for the "Missing storage body". This is impacting all of our dashboards that we use daily for cross functional review. Hopefully this can be addressed asap. Thanks for any help.
We finally started to transition to this new version, and we noticed another bug - if there is a Paragraph content, it's being cut short and not formatted. Just wondering, maybe there is a ticket for that here?
Example image: on the top - new list, below - Legacy list.
The biggest issue is that we are worried about using the Legacy list due to increasing amount of times when it freezes in loading status (image below) and new list does not show all the data, so we stuck :(
As Paulius says, cutting off after the first paragraph with no visible way of knowing you don't have the full text is very dangerous when sharing content.
It caused my team to miss a bunch of Acceptance Criteria :o
56 comments