We continue our series of blog posts related to efficient management of table data in Confluence. In the recent posts we have outlined the principles of work with the Page Properties Report macro, dynamic Scaffolding tables and data fetched from external databases. This time we will show you the technics to transform the list of JIRA Issues into the easy-to-read information.
JIRA Issue macro will help us to fetch the list of JIRA issues and transform them into the table with the user-defined columns. We are going to present you with several methods to arrange JIRA issues and get the data you really need at the moment.
So if ready, let’s start!
JIRA Issue Macro
JIRA Issue macro is a native Confluence tool that allows you to fetch the list of issues matching the entered JQL query. After inserting the macro on the page, you can select the necessary application link and then type the JQL query for issue output.
Additionally, you have several settings which can help you regulate the count of displayed issues. If needed, you can define which columns to show and which ones to hide in the generated table. This is quite flexible, especially if you use custom fields in your JIRA projects, so you can list these columns along with standard columns.
After saving the macro and saving the page, you will get a list of JIRA issues. Unfortunately, you cannot do much with them besides sorting If getting a large list of issues matching the JQL query you can always enter more specific criteria and get a smaller list. The only issue with this is a necessity to edit the page and correct your query all the time.
We used the following query:
This JQL query fetches all issues from the project JIRA Software with the component ‘Configuration’ from Atlassian public issue tracker. We have also modified the set of displayed columns and left these ones:
- Key – issue key.
- Summary – summary of the issue.
- T – icons indicating the issue type.
- P – icons indicating the issue priority.
- Status – status of the issue.
- Resolution – resolution of the issue.
- Reporter – person who reported the issue.
- Assignee – person who the issue was assigned to.
- Created – date of issue creation.
- Resolved – date when the issue was either resolved or closed.
For processing the list of JIRA issues, we will apply the bundle of macros of Table Filter and Charts add-on:
- Table Filter provides the wide set of filters for different types of data.
- Pivot Table provides the mechanism for aggregating and summarizing tables of any type in the one- and two-dimensional pivot tables.
- Chart from Table provides capabilities for generating dynamically updated charts and graphs.
So, no more talks for now. Just watch the video and find out the way to conquer your table with JIRA issues with little efforts spent.
If you have any questions, feature requests or problems with add-on configuration, drop an email to firstname.lastname@example.org and I will contact you.