Prioritizing issues
Scheduling work
On this page
Related content
- Configuring the scope view
- Re-prioritizing work items
- Configuring the scheduling of dependencies
- Showing Portfolio custom fields in Jira
- Customizing view settings
- Linking issues to parent issues
- Creating and deleting issues
- A Jira User unable to drag and drop issues in an Advanced Roadmaps Plan
- Not possible to link 2 Jira issues together via the The Parent Link field from Advanced Roadmap
- Mapping issue assignees to team members
To prioritize work for your teams, you can move an issue to a higher or lower row in the scope section. This moves the position of the issue in both the scope and timeline sections.
For instance, in the sample plan below, the issue IOS-26 is being moved from row #6 to row #5.
Prioritizing issues in the new planning experience
- In the scope section, when you move an issue that has child issues, the child issues will move with the parent issue. However, moving an individual child issue will only move that child issue.
- The ranking of child issues is independent of the ranking of their parent issues. If you rank a parent epic higher, the ranking of its child issues in Jira will stay as is. This is helpful, especially if your teams have ranked their issues in their Jira boards — the child issues will retain their ranking as is.
Last modified on Apr 4, 2019
Related content
- Configuring the scope view
- Re-prioritizing work items
- Configuring the scheduling of dependencies
- Showing Portfolio custom fields in Jira
- Customizing view settings
- Linking issues to parent issues
- Creating and deleting issues
- A Jira User unable to drag and drop issues in an Advanced Roadmaps Plan
- Not possible to link 2 Jira issues together via the The Parent Link field from Advanced Roadmap
- Mapping issue assignees to team members
Powered by Confluence and Scroll Viewport.