Table report
Report Usage
This report presents an aggregated, customizable table, where each cell displays the number of issues matching the selected row and column parameters.
ย
Specific functionality:
Both row groups (Rows Category and Group Rows by) and column groups (Columns Category and Group Columns by) can be collapsed and expanded. This enables users to focus on high-level data or drill down into specific details by revealing or hiding subgroups as needed.
Table data can be sorted by any row or group row field by clicking the sorting icon next to the row or group row header. Each click cycles the sorting between ascending, descending, and no sorting.
The table supports both total rows and total columns, displaying overall counts for each row and column. These totals can be enabled or disabled in the Display tab settings.
Clicking a cell opens a sub-table showing related issues, their total count, and a link to view them in Jira. For full guidance on how to work with subtables, see the https://grandia-solutions.atlassian.net/wiki/spaces/HUB/pages/354254952.
In the top right corner above the table, there is a filter icon. Clicking this icon opens a modal window where you can apply additional filters specific to this report. Flexible filtering allows user to manually build additional issue query using multiple filters including Jira system and custom fields.
Setting up a report
The report has 5 tabs of configurations: Data source, Parameters, Display, Subtable, Description.
Data source, Subtable & Description
This report supports filtering issues by Basic Source, Saved Filter, or JQL query. For full guidance on how to configure your data source, subtable and description, see the https://grandia-solutions.atlassian.net/wiki/spaces/HUB/pages/352092236
Specific Report Parameters
Rows Category lets the user select the main field to categorize table rows. This is a required field and determines how the data will be grouped vertically.
Columns Category lets the user select the main field to categorize table columns. This is a required field and determines how the data will be grouped horizontally.
Group Rows by (optional) allows you to group data within each row (main group), providing a more detailed breakdown inside every row category.
Group Columns by (optional) allows user to group data inside each main column for a more detailed view.
The Period field sets the time unit (default: โAll timeโ). For Days, Weeks, or Months, users can also select a reference date field (e.g., Created, Status Category Changed) to define how time-based data is reported.
Display
Show Empty Rows/Columns toggle allows the user to display or hide rows and columns that do not contain any data in the report. When enabled, all possible row and column groups will be shown, even if they are empty.
Total by Columns โ enables the calculation and display of the total value for each column at the bottom of the table. When enabled, a summary row with totals will be added.
Total by Rows โ enables the calculation and display of the total value for each row at the end of the table. When enabled, a summary column with totals will be added.
Report Use Cases
โ Visualize progress towards a release goal.
Rows Category: Fix Version
Columns Category: Status
Group Rows by: Issue Type
โ Compare bugs to total issues in each release / sprint.
Rows Category: Fix Version / Sprint
Columns Category: Issue Type
Group Rows by: Priority
โ Track issue completion within each epic.
Rows Category: Epic Link
Columns Category: Status
Group Rows by: Issue Type
โ Identify how the scope of each release has changed over time.
Rows Category: Fix Version
Columns Category: Created
Group Rows by: Issue Type
Period: Week by Updated
โ Review team performance and sprint effectiveness.
Rows Category: Assignee
Columns Category: Sprint
Group Columns by: Status
โ Check what is pending for QA and who is assigned.
Rows Category: Epic Name
Columns Category: Assignee
Group Rows by: Issue Type
JQL: Status = โReady for QAโ