• +(91) 8750050183
  • info@helpingtesters.com
  • helpingtesters

Generating Reports in JIRA

August 12, 2017
JIRA Reports, Reports in Jira, Generate Report in Jira

JIRA is well known for defect tracking and project management. And one of the facets of project management is to monitor various reports provided by JIRA. The well-known defect tracking tool allows you to create a number of different reports which can help you get an overview of the current status of the project. These JIRA reports, through pictorial depiction, helps you translate the current defect status and progress of various issues in the project. Some reports are in the form of charts, line-charts, bar-graphs, to name a few.

Topics under Complete JIRA Tutorial Series

That’s not all, for easy accessibility, the reports can also be shared with different team members or can be extracted for future reference. All you need is the right authorization and you are good to go. In this article, we would first know about how different team members use JIRA reports and then look at the different types of reports available.

How different Team Members use JIRA Reports

Just like different team members have different roles in the project, each of them uses JIRA reports in different ways.

  • Developers – Developers use JIRA reports to get a brief overview of the number of bugs that were reported against the features that were assigned to them. As such metrics are often considered for KRA (Key Responsibility Area), such reports help developers get an overview of their current expertise and the amount of quality they are adding to the project.
  • Testers – As testers are mostly responsible for logging defects, they extract the bug reports of different projects to find out how many bugs they have logged over a period of time. Apart from that, they can also get a pictorial overview of the number of production issues encountered against the features they had originally tested.
  • Project Lead/ Manager – The project manager or lead can either utilize the above-mentioned reports to evaluate the competencies of developers and testers or device other tactics to create a custom report to find the effectiveness of the team members. Apart from this, the project manager also has to submit reports to higher management or clients and publish reports of the defect and issue slippages during a sprint.
  • Clients/ stakeholders – As clients or stakeholders can’t look into each and every issue or the minute aspects of the project, they use these charts extensively to get a grasp of the project proceedings. They generally refer the flow chart and burn down charts to correlate the performance of one sprint with another. They can also use the reports from JIRA to evaluate the success of a release by comparing it with previous releases.

Depending on the importance of the reports, they are stored or archived for future reference.

Different JIRA reports

What are the different JIRA Reports

JIRA allows you to create different types of report. Some of the most frequently used are:

Average Age Report

The average age report is a bar chart, which shows the average age of unresolved issues in days, at a given point of time. The report generated depends on the selected project, type of issue selected in the filter, and the chosen unit of time (hours/ days/ week/ months e.t.c.).

Average age report

  • To create average age report, you need to first select the project and click on “Summary” tab.
  • Then navigate to “Reports” section and select “Average Age Report”. Once the report type is selected, you have to choose the desired filter/ project.

Average age report filters and selections

 

  • Use the “Period” field to specify the timeframe on the basis of which the report would be generated.
  • Use the “Days Previously” field to specify the number of backdated days, whose data would be used for report generation.

Created vs Resolved Issue Report

This report is a difference chart which shows the number of issues resolved and the number of issues created within a timeframe.

Created vs resolved issue report

  • To create a created vs resolved issue report, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “Reports” section and select “Created vs Resolved issues Report “. Once the report type is selected, you have to choose the desired filter/ project.

Customizing Created vs resolved issue report

  • To customize the report, you have to enter various parameters. Use the “Period” field to specify the timeframe on which the report would be based.
  • Use the “Days Previously” field to specify the number of backdated days, whose data would be used for report generation.
  • In the “Cumulative Total” field, select “Yes” if you want to progressively add data to the preceding column. Select “no” if you want to show a single value in each column.
  • Use the “Display the trend of Unresolved?” to specify if you want to display the number of resolved issues in a subplot (by selecting “Yes”).
  • The “Display Versions?” field is used to specify which version dates you want to track in the Created vs resolved issue report. Selecting “All version” would display all version dates in the report, while ” Only major versions ” will only consider the major version release dates (in x.x format). In case “None” option is selected, release dates won’t be displayed in the report at all.

Pie Chart Report

The pie chart report is used to display a filtered list of issues grouped by a specific field.

Pie chart report

  • To create a Pie chart report, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “Reports” section and select ” Pie chart report “. Once the report type is selected, you have to choose the desired filter/ project.

Generating a pie-chart report

  • Once the filter is set, you have to use the “Statistic Type” field, to specify the grouping criteria of the filtered issue list.

Resolution Time Report

The resolution time report is used to depict the average resolution time of issues. Such reports can be used to find out the trends in resolution time.

Resolution time report

  • To create a Resolution Time Report, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “Reports” section and select ” Resolution Time Report “. Once the report type is selected, you have to choose the desired filter/ project.
  • Use the “Period” field to specify the timeframe on the basis of which the report would be generated.

Resolution Time Report

  • Use the “Days Previously” field to specify the number of backdated days, whose data would be used for report generation.

Recently Created Issues Report

This report consists of a bar chart which shows the rate at which new issues are created and how many issues are resolved during that same interval.

Recently created issue report

  • To create a Recently Created Issues Report, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “Reports” section and select ” Recently Created Issues Report “. Once the report type is selected, you have to choose the desired filter/ project.

Recently created issue report

  • Use the “Period” field to specify the timeframe on the basis of which the report would be generated.
  • Use the “Days Previously” field to specify the number of backdated days, whose data would be used for report generation.

Single Level Group by the Report

This report returns issues matching the search criteria which would be grouped by a specific field. The single level group by report won’t give show you a chart but simply categorize and group your results.

Single level group by report

  • To create a Single level group by the report, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “Reports” section and select ” Single level group by the report “. Once the report type is selected, you have to choose the desired filter/ project.
  • Once the filter is set, you have to use the “Statistic Type” field, to specify the grouping criteria of the filtered issue list.

Time Since Issues Reports

The Time since issues report is a bar chart which shows the number of issues of any specific status (Created, updated, Resolved, e.t.c.) was set on a given date. The report generated is based on the unit of time (hour, days, weeks, month or years) chosen by you.

Time since issues report

  • To create a Time since issues report, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “Reports” section and select ” Time since issues report “. Once the report type is selected, you have to choose the desired filter/ project.
  • Use the “Date Field” to select the desired date. This option is only available if time-tracking has been activated by your administrator.
  • To customize the report, you have to enter various parameters. Use the “Period” field to specify the timeframe on which the report would be based.

Time since issues report

  • Use the “Days Previously” field to specify the number of backdated days, whose data would be used for report generation.
  • In the “Cumulative Total” field, select “Yes” if you want to progressively add data to the preceding column. Select “no” if you want to show a single value in each column.

Time Tracking Report

This report shows the time estimates for various issues of a project. The report shows the originally estimated time and the time actually taken to accomplish the task in hand. It also shows on the basis of time tracking information whether you are behind or ahead of actual schedule.

Time tracking report

  • The report has four different tracking fields
    • Original estimate – The original estimate field states the time estimate provided during sprint planning meeting to complete the task in hand.
    • Estimated Time Remaining – It shows the current estimated time remaining to complete the issue
    • Time spent – It shows the amount of time that already has been spent working on the issue. The time spent is the aggregation of all the time logged for a particular issue.
    • Accuracy – Accuracy is calculated by summing the “Time spent” and “Estimated time remaining” and subtracting it from the “Original Estimate”. If the accuracy is 0, your task is going as per schedule, if it is positive, you are ahead of schedule. If accuracy is negative, or the summation of time spent and time remaining is greater than the original estimate, then you are behind schedule.
    • Progress bar – The progress bar shows the number of completed issues in green, and the number of incomplete issues in Orange.
  • To create a Time Tracking report, you have to navigate to the project of your choice and choose “Reports” in the sidebar.
  • Then select, “Forecast and management” section and click on “Time Tracking report”.
  • Use the “Fix Version” drop-down, to select the issues pertaining to a certain version for which the report would be generated. If you want to create the report for issues spanning across any and all versions, select “No Fix Version”.
  • Use the “Sorting” drop-down to specify, how the issues in the report would be sorted.
  • By selecting the “Issues” drop-down, you can specify which issues from the selected version would be part of the report. If you select, “Incomplete issues only”, completed issues and issues for which time hasn’t been tracked would be excluded from the report. On selecting “All”, every issue, from the selected version, irrespective of their status would be included in the report.
  • By using the “Sub-task Inclusion” drop-down you can specify which sub-tasks you want to include in the report. You can select sub-tasks from a certain version, sub-tasks which don’t have any version or all sub-tasks.

The JIRA reports mentioned earlier can be accessed by anyone, but the ones listed below can only be viewed if time tracking is enabled by your JIRA admin.

User Workload Report

The user workload report is used to display time to track information for a particular user. Using this report you can find out the number of unresolved issues assigned to a particular user and the remaining workload on a per-project basis.

User workload report

  • To create a ” User workload report”, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “JIRA Reports” section and select ” User workload report “. Once the report type is selected, you have to select the “User”, for whom the report would be generated.

User workload report

  • By using the “Sub-task Inclusion” drop-down you can specify which sub-tasks you want to include in the report. You can select sub-tasks which are assigned to a specific user or sub-tasks regardless who the assigned user is.

Version Workload Report

The version workload report is used to view the list of unresolved issues assigned to different users, their workload, and the summary of the total workload remaining for the selected version.

Version workload template

  • To create a “Version workload report”, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “JIRA Reports” section and select “Version workload report”. Once the report type is selected, you have to select the “Version” for the report.
  • Use the “Display unestimated issues”, to select which issues should be included in the report. On selecting “Yes” all issues regardless of their estimated time remaining and original estimates would be shown in the report. While selecting “No”, would only show issues whose “Original Estimate” is missing.

Version workload template

  • By using the “Sub-task Inclusion” drop-down you can specify which sub-tasks you want to include in the report. You can select sub-tasks from a certain version, sub-tasks which don’t have any version or all sub-tasks.

Workload Pie Chart JIRA Reports

The workload pie chart JIRA reports is used to display relative workload of assignees in a particular project or issue filter.

Workload pie chart report

  • To create a Workload pie chart report, you have to navigate to the project of your choice and click on “Summary” tab.
  • Then navigate to “JIRA Reports” section and select ” Workload pie chart report “. Once the report type is selected, you have to choose the desired filter/ project.

Workload pie chart report

  • Use the “Statistic” drop-down to select the field on the basis of which, the pie-chart would be created. Click “Next” to create the pie-chart.

 

Additional JIRA Reports

  • The above-mentioned JIRA reports are some of the reports that are often used by users. But JIRA allows you to create or download even more reports and integrate them with JIRA.
  • You can add other reports like Gantt Chart Report, Timesheet Report, JIRA SQL Plugin, e.t.c. by downloading them from the Atlassian Marketplace.
  • JIRA administrators can even create new JIRA reports from scratch using the plugin API.
  • Another way of creating custom reports in JIRA is by creating a custom filter and extracting the search results in an excel sheet. Once the data is extracted, it can be further manipulated to create charts and reports from MS Excel itself.

 

Conclusion

  • There are a number of different JIRA reports which can be created. All you need to do is select the criteria and select the report of your choice.
  • JIRA Reports help team members, project managers, and even clients to get a brief overview of the ongoing project by looking at the charts and diagrams.
  • These reports can be easily extracted and shared in different formats. That’s not all, JIRA administrator can also add other reports from JIRA marketplace or create their own reports using the plugin API.

Leave a Reply

Your email address will not be published.

Broaden Your Knowledge. Enroll Today.

Our tutoring services on software testing courses online offer information on a wide variety of courses, ranging from Web Security and Software Testing courses to selenium online training to Mobile Automation Testing. Whatever criterion you need help with concerning advanced technological functions and operations, we’ve got you covered. We also use real world examples and scenarios for solving examples and projects, enhancing your knowledge and broadening your horizon.