Card report

Card report

Report Usage

This report comes in the form of a card report. The card report was implemented to provide a concise summary of key metrics, making it easier for users to quickly assess performance and identify issues. By grouping data into individual cards, users can easily track different metrics without navigating through complex charts or tables.

Screenshot 2025-04-01 at 10.42.04.png

Specific functionality:

  • Single cards can display a customized data source and a status threshold (e.g., OK, Problem, Warning), providing a visual cue to highlight potential issues or positive trends and enabling faster decision-making.

  • Expandable cards offer deeper data analysis by breaking down statistics (e.g., by assignee). Users can reveal full details by clicking the top-right button on each card.

  • By clicking any card the user is able to open a table with its detailed issue view.

  • Additionally, the user can view the total number of issues for the selected metrics or statistic type within the chosen configuration, along with a link to the list of these issues in Jira (View in Issue Navigator).

Screenshot 2025-04-01 at 10.53.20.png

Setting up a report

The report has 4 tabs of configurations: Data source, Parameters, Subtable, Description.

Data source

Configure and manage the source of data for generating reports.

Снимок экрана (1731).png
The project field lets the user choose from which project issues will come from. By default, it is set as a project where the app was opened.
Снимок экрана (1732).png
The saved filter field lets the user filter issues by existing filters.
Снимок экрана (1016).png
The JQL field lets user filter issues by using JQL requests. The report uses Atlassian’s JQL component so it has syntax checking and auto-complete implemented. When the user finishes inserting the JQL the user can validate the JQL using the button underneath the input. Number of issues is clickable. By clicking, the user is redirected to the page with a list of issues in the Jira project.

Parameters

Allow users to tailor the report to their specific needs and preferences.

Screenshot 2025-03-25 at 18.06.09.png

Metric - defines the type of data from Jira issues that should be used for calculation. The options include available fields in the current Jira instance.

Screenshot 2025-03-25 at 18.19.32.png

Calculation method – defines how the metric value is calculated. Options include count, sum, and average.

Statistic type – defines a category or classification for organizing and presenting project-related data.

Warning threshold – sets the value that will trigger a warning or problem status when the calculated value exceeds it. (This parameter is disabled if a statistic type is selected.)

Problem threshold – sets the value that will trigger a problem status when the calculated value exceeds it. (This parameter is disabled if a statistic type is selected.)

If the calculated value exceeds neither the warning nor the problem threshold, the status will be ‘OK’.

When Custom Data Source is specified for the card, it will override the regular data source.

Subtable

This tab lets the user manage the display of columns in a subtable by adding, removing, or rearranging them.

subtable.png

 

Columns let the user manage the display of columns in the table of the report by adding, removing, or rearranging them.

Custom fields let users add any field from Jira to the list of columns of the report table.

Description

It serves as a space where users can provide context, explanations, and additional information about the report.

Снимок экрана (1736).png

Description lets user add any additional information no more than 500 characters about the created report.
The description will be presented directly on the report card above the chart (in case of its presence).