Sort issues in Advanced Roadmaps
By default, issues in a plan are sorted by issue ranking. You can also sort issues by the following:
If you’re using the Advanced Roadmaps app (version 3.29 or earlier) from the Marketplace, some of the options listed in this section may not be available in your instance.
Configure sorting order
Navigate to the View settings menu, then use the Sort by dropdown menu to change how issues are sorted in your plan.
To toggle between ascending and descending order on your roadmap, select the up or down arrow next to the field by which you’d like to sort your plan. If issues are already sorted in ascending or descending order, a reset icon will appear at the top of the Fields column. This icon will revert issues to the default rank order.
Rules on sorting issues
Regardless of how sorting is configured in a plan, the following rules still apply:
- The order of issues is determined by the sorting method, and will overrule any drag-and-drop adjustments you make to your plan.
- Issues will be sorted based on the highest hierarchy level shown in your timeline. Child issues will be sorted in the same manner, but still grouped under their parent issue.
- Issues in your plan will be sorted by the field of your choice, regardless of changes you make to other fields.
- Newly created issues in your plan will be sorted according to your defined sorting rule.
Sort issues by:
There are three dates by which you can sort your issues: target dates, due dates, or custom dates. These different dates are all treated the same way in Advanced Roadmaps, so we simply refer to them as dates.
When sorting issues by dates, keep the following rules in mind:
- Sprint dates will be used if an issue doesn’t have a start or end date but is assigned to a sprint.
- Adjusting the dates of issues will change how these issues are sorted in your plan.
Regardless of whether you’re using story points or time estimates (days and hours), the following rules apply:
- Issues without an estimate will be sorted as though they have an estimate of zero.
- Issues that have rolled-up estimate values will be sorted by the total estimate value of a parent issue plus its children.
- If you change the estimation units of your plan, issues will revert to the default sorting order.
When you sort issues by status, the following rules apply:
Issues will be sorted by status within their parent hierarchy level. Issues with the same status type will be ordered alphabetically.
Issues created in your plan that haven’t been saved to Jira Software are sorted above those already saved when in ascending order.
To sort issues by priority, the projects in the plan must use the same priority scheme. If they're not, the option to sort by priority will be disabled.
Assignees and teams
Unassigned issues will be grouped together at the top or bottom of your plan, depending on whether you’re using ascending or descending order.
Custom field values
You can sort issues by the values of the following custom fields:
- date picker
- user picker
- radio button
- single-choice select
- multiple-choice select
- single-line text
Issues without a custom field value will appear first or last, depending on whether you're sorting in ascending or descending order.
If the custom field is removed from the plan while being used, the issues will revert to rank order.
Was this helpful?Yes Provide feedback about this article