Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Problem

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

...

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:

      Code Block
      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

...

  1. Remove the orders or filters applied to the report, and check for the report's display

...

  1. . In the case described, the user was altering the display of the report by adding an “order by” clause in the JQL.

Info
  • Hierarchy reports are not meant for sorting