ποΈ Navigation |
|---|
Report Usage
This report comes in the form of table reports. It provides users with a list of issues in a structured hierarchy (For example: Epic β User Story β Sub-task). Its primary objective is to showcase issues in a rolled-up format, where child issues contribute to the totals of their parent issues.
.png?version=1&modificationDate=1710161665426&cacheVersion=1&api=v2&width=760&height=342)
The Report table consists of the following default columns:
Key: Contains clickable issue key, by clicking on it user will be redirected to this issue in Jira.
Progress bar: A bar showing the degree of task readiness.
Summary: Brief overview of an issue.
Specific functionality:
At the top of the report card from the left side, we have the total number of issues within selected configurations.
Clicking on any column header will sort either from the highest to the lowest value, or from A to Z and vice versa.
From the right side at the top, there is an issue search. User can filter issues by key or summary.
Using the hierarchical distribution of issues, the user can view all child issues by clicking an arrow next to the parent issue.
Each issue that has child issues can additionally have a progress bar. This option is configurable.
If an issue has a parent issue, then in its summary there will be a clickable link to its parent issue.
If report contains issues without parent, they will be placed in a separate dropdown.
Setting up a report
The report has 4 tabs of configurations: Data source, Parameters, Display, Description.
Data source
Configure and manage the source of data for generating reports.
.png?version=1&modificationDate=1719400453789&cacheVersion=1&api=v2&width=362&height=170)
.png?version=1&modificationDate=1719400516305&cacheVersion=1&api=v2&width=362&height=170)
.png?version=1&modificationDate=1710403483879&cacheVersion=1&api=v2&width=573&height=234)
Parameters
Allow users to tailor the report to their specific needs and preferences.
.png?version=1&modificationDate=1719401579473&cacheVersion=1&api=v2&width=380&height=138)
The Hierarchy field is required. It defines hierarchy levels for chosen issues.
Display
Manage the visual appearance and presentation of the report, including the visibility of specific elements and the formatting of data.
.png?version=1&modificationDate=1719401651443&cacheVersion=1&api=v2&width=504&height=208)
The Columns block gives a user the possibility to customize the sequence of columns and remove unnecessary ones to suit their preferences for a personalized view of data.
Custom fields is a multi-select field. It allows users to add additional fields to sub-table columns.
Fields are categorized as Rollable or Non-Rollable based on their type. This distinction influences how values are displayed in the table.
Rollable Fields: Numeric fields, such as "Story Points" and "Original Estimate," are considered Rollable. When you select these fields, they will appear as individual columns in the table. If a value in a Rollable field is a rolled-up value, a sigma (Ξ£) icon will be displayed to the left of it. This icon indicates that the value is a sum of estimates from child issues. If the value is not rolled up and is specific to the issue itself, it will be displayed without the sigma icon.
Non-Rollable Fields: Fields that are not numeric, such as "Assignee" and "Labels," fall under the Non-Rollable category. These fields provide context and details about the issues but do not participate in the rollup calculation.
Description
It serves as a space where users can provide context, explanations, and additional information about the report.
.png?version=1&modificationDate=1719401727945&cacheVersion=1&api=v2&width=614&height=224)
Description lets the user add any additional information no more than 500 characters about the created report.
The description will be presented directly on the report card (in case of its presence).