Problem
A hierarchy report was created following the Epic - Task - Sub-task relationship. The information should show the issues following that order, but the report shows some sub-tasks twice or out of place.
Solution
Review the fields and any filters or JQL applied to them. In this case, the customer used the following fields and JQL:
Issue Type
Issue Key
Assignee
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
Remove the orders or filters applied to the report, and check for the report's display. 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