Jira Report

[AJ Colubiale]

Previously I was able to use Jira reports to populate a changelog of what was worked and completed in each sprint. Lately, this feature has not been working as expected. When I select Jira Report and I add the appropriate filter for the report I want to see, I am served a blank page. It seems as though your new templating feature is not working for Jira Reports. Can you please fix this, or help me figure out how to make this work so I can continue to help my team keep historical record of changes and it's velocity effectively?

Thanks,

AJ

[Pierre Lemay · Accepted solution]

@AJ Colubiale ,

   I just found out that a duplicate question has been raised already which proposed a workaround that is working for me, i.e. simply save the blank page... to see its content appearing!!

Please refer to this question: https://community.atlassian.com/t5/Confluence-questions/Jira-Reports-Change-log-is-now-blank/qaq-p/1363472

Also, in the JIRA ticket mentioned by Atlassian representative, make sure to click on "This affect my team" to have your count.

[AJ Colubiale]

Thanks, @Pierre Lemay!

[Diego]

Hello @AJ Colubiale !

As I understand, some Jira macros in Confluence are not working as expected. Since I was unable to replicate the behavior, I would like to ask you a few questions.

Here we go:

1. Are you referencing the Jira Charts Macro?
2. Are you referencing the Jira Issues Macro?
3. Would it be possible for you to share some screenshots of the behavior with us?
4. Is this happening with already existing Jira Macros?
5. Is this happening with newly created Jira Macros?

When taking the screenshots, be sure not to disclose any sensitive information with them. The Community is an open space and everyone can see everything posted here.

Looking forward to your reply!

[AJ Colubiale]

This is a page template I am referring to as seen below:

When I select 'change log' and add my filter, this page no longer renders the components it used to.

[Pierre Lemay]

Wow, this has a huge impact as I was using this every time we released a new version of the product.

Is this broken or a new approach is recommended now with the new editor ?