Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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.

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.

  • No labels