Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.
×Hi everyone
My company recently switched to Jira Cloud Enterprise.
The idea was to have this 4 hierarchy level: Epics > Story > All standard issue type except Story > Subtasks.
We did the following so far (thanks to a community answer, don't remember who it was)
The timeline used to display "epic" (lvl 1) followed by "story" and all other standard issue types (lvl 0). Now this timeline starts at "story" (lvl 1) followed by all standard issue types (lvl 0). How can we make the hierarchy lvl 2 (epic) appear in our timeline?
We didn't filter for any issue types in the board settings and have no columns contraints. Could be someone in the project default settings that needs to be adjusted? Screens, Fields or Permissions?
Hello @N_ S_
Welcome to the Atlassian community.
Are you viewing a Timeline that is part of a Plan created through the Plans menu?
Or are you viewing a Timeline that is directly available from the navigation options on the left while you have an agile board displayed?
If you are using the second type of Timeline, you are experiencing expected behavior. That Timeline offers only basic features. It can show only Level 1 and Level 0 issues. To see issues at Level 2 and higher you need to use the Plans feature and view the timeline available through it. For more information about Plans refer to
https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-roadmaps/
I meant the second type of timeline. I see. I was hoping that there was a way to edit that timeline, to not introduce too many new things to my team.
Thank you for your response anyway, because now I can tell them, there is no way around learning to use the plans and hide the former timeline.
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.