We are working in a Company Managed Project. The work items in my backlog appear to be a dump or all Epics Storys Tasks and Subtasks, how can I get the backlog to display in a usable parent/child format?
Hello @Terry DeGraeve
Welcome to the Atlassian community.
Are you working with a Business, Software, or Service project?
Is the board a Kanban board or a Scrum board?
Can you provide a s screen image of what you see, obscuring the details so that we can see the issue types/icons for the items?
This is a software project, on a Kanban board. I have 129 items in my backlog that is just a list.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the board a Kanban board or a Scrum board?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a Company managed software project, using a Kanban board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for that additional information.
The backlog will show nesting of child issues only for sub-tasks under their parent issue. No other parent/child relationship nesting can be displayed in the Backlog issue list.
You can see nesting of child issues under their Epics if you use the basic Timeline view available from the navigation panel on the left.
If you have extended your issue type hierarchy about the Epic level, the only native method to see the nesting of Epics under higher level issues is to create an Advanced Roadmap Plan through the Plans menu, and use the Timeline view available there.
What problem are you trying to solve by showing issue nesting in the Backlog list? The general purpose of the backlog list is to drag and drop issues to reorder them to show the priority order for the work to be done. If issues are nested under their parents, you lose the ability to prioritize the work at any level but the highest and then the lowest level within a single issue hierarchy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.