Card View

The Card View offers a visually appealing and interactive way to display your hierarchy and related data. Follow these steps to set up and use the Card View efficiently:

Step 1: Set Your Filters

• Begin by selecting project filters from the dropdown menu to narrow down the issues you want to include in the hierarchy.

• Alternatively, apply a JQL query in the same dropdown menu to define custom filters.

• This ensures that only relevant data is included in your report.

Step 2: Configure the Hierarchy Levels

• Once the filters are set, configure the hierarchy levels located just below the filter section.

• By default, the first three levels are available for hierarchy setup. You can add more levels by clicking the plus icon.

• Drag and drop issue types to arrange them in the desired sequence.

• Multiple issue types can be added to each level, and any issue type can be removed by clicking the cross icon.

• After making changes, the hierarchy configuration and Card View will update automatically to reflect the changes.

Step 3: Review the Card View

• The data will be displayed in a card-based format, where each issue type is represented by a card showing key details.

• Cards are grouped by their hierarchy levels, making it easy to visualize relationships and dependencies.

Interactive Features:

• Rearrange or edit hierarchy configurations directly from the Card View as needed.

• View key issue attributes, such as status, summary, and assignee, prominently displayed on each card for quick reference.

Real-Time Updates:

• Any changes made to hierarchy levels or filters are reflected instantly in the Card View.

Exporting the Report:

• The report can be exported to a CSV file using the Export icon located to the right.

Reading the Exported Tabular Report

In the exported report, each main issue is presented in a row, with child rows for each of the linked issues. The selected jira fields are exported to the file for each (linked) issue, presented as columns following the issue’s key.

For example

• Row 1 is read as, TP-1 Relates to TP-4, TP-6 and TP-4 is linked with TP-12, TP-27 and TP-6 linked with the (Need SS to update the data)

Additional Notes:

• Currently, all features remain the same as the Tabular View, with the Card View UI introduced as an alternate representation.

• If the hierarchy has already been configured in the Tabular View, switching to the Card View retains the same data—only the visual representation changes.

• Preferences are saved identically across both views, ensuring seamless transitions.

The Card View provides a structured, user-friendly representation of your hierarchy, enabling efficient review and management of issues.