Skip to end of banner
Go to start of banner

WIP: Hierarchy report doesn't display sub-tasks correctly

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

« Previous Version 2 Next »

\uD83E\uDD14 Problem

A hierarchy report was created following the Epic - Task - Sub-task relationship. The report should show the issues following that order, but some sub-tasks are shown twice or out of place in the report.

\uD83C\uDF31 Solution

  1. Review the fields and any filters, or JQL applied to them. In this case, the customer used the following fields and JQL:

    1. Issue Type

    2. Issue Key

    3. Assignee

    4. Some other Custom Fields.

JQL used: Project = REQ AND statusCategory != "Done" and id != "REQ883" AND (labels in ("bp-high", "ProblemStatement") OR component in ("Game)) order by [Projected Into QA Date] ASC

2. Remove the orders or filters applied to the report, and check for the display of the report. In the case described, the user was altering the display of the report by adding an “order by” clause in the JQL.

Hierarchy reports are not meant for sorting

  • No labels