nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automating JIRA Reports - Ideally to Confluence

Andrew Sedlacek

Hey all! I'm trying to help automate our weekly Sprint Review and our Product Updates. I'm trying to figure out a way to automate a few things:

1. Summarize all tasks completed in the weekly Sprint.

2. Sprint completion report - highlight which products were affected (i.e. new functionality, bug fixes, etc) for our engineering team.

3. Translate this into a Confluence document each week, which I can then use to send updates to our entire company.

Accepted answers

Nikola Perisic

Welcome @Andrew Sedlacek

When you say summarise, does this mean summarising the content of the issues completed within the sprint or to have the list of the issues completed during weekly sprint? For summarising the content of all of the issues could be actually done if you have one Epic that contains the user stories and then use the Atlassian Intelligence to summarise everything, otherwise it is not feasible. If you want to have the list of the issues, you can use the JQL:

project = PLAT AND sprint in openSprints() AND statusCategory = Done

2. For sprint completion report, use the Sprint Report which contains work completed or pushed back in the backlog in each sprint. Jira doesn't have the ability to create automation that as an action will create the report, so this would have to be done manually.

3. Due to limitations in Jira, for sprint reports, you can share the report with other users within your company. This would also have to be done manually. For this you can also check this page: https://www.reddit.com/r/jira/comments/18lkni3/jira_automation_rules_for_confluence_page_with/

All comments

Nikola Perisic

Welcome @Andrew Sedlacek

When you say summarise, does this mean summarising the content of the issues completed within the sprint or to have the list of the issues completed during weekly sprint? For summarising the content of all of the issues could be actually done if you have one Epic that contains the user stories and then use the Atlassian Intelligence to summarise everything, otherwise it is not feasible. If you want to have the list of the issues, you can use the JQL:

project = PLAT AND sprint in openSprints() AND statusCategory = Done

Andrew Sedlacek

Ok awesome, this is super helpful!

Is it possible to modify the Sprint Reports? It doesn't appear to show the Epics, which would be great.

I'm actually looking to summarize both 1. issues completed and 2. content of those issues. I want to communicate to the team "This is how Epic X changed this week, here are the new features, here are the bug fixes".

Again, ideally, then have a Sprint Report document automatically created in Confluence to summarize everything into a product-by-product update, showing new features, bug fixes, etc.

Toying with the idea of creating an Agent to basically review the Confluence Sprint Report and create a nice bullet point document with some intro/analysis in human language.

Nikola Perisic

By default you cannot modify the reports in Jira, you would need a third party app for this like eazyBI. To summarize the content of the issues and issues completed could be done with the usage of Atlassian Rovo.

Andrew Sedlacek

Ok great, thank you Nikola!

Danut M _StonikByte_

Hi @Andrew Sedlacek,

You could create a report page in Confluence with the necessary macros that pulls data from Jira. You could use the macros available in Confluence (Filter results, Sprint Health, Sprint Burndown, Pie Chart, etc). And if you need more, you could search for a plugin from Atlassian Markeplace that provides the gadgets/macros you need.

In case you want to use a plugin, have a look over our Great Gadgets for Confluence Cloud. It offers many macros for tracking sprint data.

For displaying the issues from sprint under their parent epic, you could use the Pivot Table & Pivot Chart macro/gadget - this allows you to group the issues from sprint by various fields, including epic, product etc

Or maybe you can use the Team Wallboard macro/gadget configured to display swimlanes by Epic. The app offers many other charts like burndown, burnup, velocity, wbs, etc - all you need for a complete sprint report. See more in these articles:

If you have any questions about these macros/gadgets, feel free to contact us at support@stonikbyte.com.

Danut.

Alexey Pavlenko _App Developer_

Hi @Andrew Sedlacek ,

For items 1 and 2 you can use the app I developed - Multi-team Scrum Metrics & Retrospective. If you need only the completed scope - you can toggle off all other metrics. If you need to display only 1 board/team and only for the last sprint - you can configure it, so that only the last sprint will be automatically shown every time. Columns of tables are customizable; you can choose which columns to display.

For the 3rd item - you can either screenshot it and insert it to your Confluence page manually or I can implement this feature for you.

Best regards,
Alexey

Javier Coira _Appfire_

Hi @Andrew Sedlacek ,

I’m Javier Coira, a developer for Dashboard Hub. I think the other options suggested are great, whether using Confluence’s native macros or apps. However, given the specificity of your case, I’d like to suggest some functionalities of Dashboard Hub (which you can use both in Jira and Confluence).

1. Summarize all tasks completed in the weekly Sprint.

For this case, you can use the Sprint Burndown, Sprint Goals, or Sprint Health gadgets, or leverage a Jira Custom Chart to visualize sprint-related data in various formats (Pie Chart, table, bar chart, etc.) (Project and Issue Tracking documentation)

Let me share with you this example, where you can see different metrics from different sprints (in this case, in Jira):

Screenshot 2025-03-19 at 21.09.29.png

You can also compare sprint velocity with previous sprints using the Scrum Velocity gadget.

Screenshot 2025-03-19 at 21.11.26.png

2. Sprint completion report - highlight which products were affected (i.e. new functionality, bug fixes, etc) for our engineering team.

To track which products were impacted, I recommend using the Time in Status and Progress Tracker gadgets. These will give you insights into issue progression and time spent in each workflow stage.

Additionally, Jira Custom Charts is the most versatile gadget for this purpose. With the right configuration, you can filter by issue type (e.g., new functionalities, bug fixes) and display data in multiple visual formats tailored to your needs.

Progress Tracker:

Screenshot 2025-03-19 at 21.25.57.png

Time in Status:

Screenshot 2025-03-19 at 21.28.07.png

Finally, there is an option to export DH dashboards to PNG or PDF. However, if you just want to share the dashboards, you can use shared links.

Feel free to ask any further questions and good luck!
Regards

John Funk

Hi Andrew - I am marking Nikola's answer as accepted. Please let us know if you still have questions.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira

cloud

jira-cloud