Thanks for mentioning at 4:24 that the hierarchy only works for the premium plan! Most tutorials take for granted, that you own the maximal plan for everything
For everyone seeing this video in 2024. Advanced Roadmap hierarchy configuration was replaced by Issue Type hierarchy. You can still create issues above Epics as long it is on top of Epic issue type on the list. There's a bug that when you create a new issue type (Initiative or Legend), it shows up as 2 in the hierarchy level and Epic as 1 and you can't change the order. Just Save Changes and it will work as intended (very confusing I know.)
I really need to go back and update these videos. I've been waiting for Atlassian to drop a new feature that will change how all of this works before I invest time into redoing this.
hi , first thanks for all your amazing videos. i started to manage the jira issues in my company with no knowledge at all and you save me. i have a question, i can see that in the advanced roadmap hierarchy its notifying you that this change will affect all plans, what does it mean? if i dont want something above an epic in some projects, will it affect them somehow?
@@ApetechTechTutorials in the Advanced Roadmaps hierarchy configuration what matters for the hierarchy to work in the way i want is the numbers(1,2,3) or their position in the hierarchy (from top to bottom) ?
Adding an initiative issue type will be treated as a regular issue type. You'll want to exclude them from your board so that don't impact your sprints and reports.
Hi there. Is it possible to have two level different level names with the same level issue type? in other words, can I have one initiatives under another initiative?
I have followed all the steps, however, on my issue type hierarchy page, I am unable to move Phase (my new issue type) above Epic. As in, Epic is automatically numbered 1, with the new issue type 2 automatically. How can i make Phase the parent of Epic?
Same problem here. Posting in case someone else stumbles across this in the future. Also interestingly, when I click "Advanced Roadmaps hierarchy configuration," instead of what we see in the video, it takes me to "Issue Type Hierarchy." Despite all of those issues it still works. For some reason the numbering is reverse order. So if you've made a new issue type to be above epic and its numbered "2," that's ok! As long as you have it positioned above the Epic level it should work.
Dang Man - you BABBLE on SO MANY TIMES about so many of your previous videos that I keep forgetting what the hell I am trying to solve. A little more focused conversation would be helpful
Hector, I appreciate your comment. The material that was required/needed to cover the topic of this video was covered in the video. Supplemental videos are created to cover other topics that might be related. As you may know, UA-cam favors smaller, specialized topic videos. But, since I see you have some interest, I could cover this entire topic end-to-end in one of my future live streams.
To get more resources and get in contact with me check out this link linktr.ee/apetech
Thanks for mentioning at 4:24 that the hierarchy only works for the premium plan! Most tutorials take for granted, that you own the maximal plan for everything
It's the little details that make all the difference.
For everyone seeing this video in 2024. Advanced Roadmap hierarchy configuration was replaced by Issue Type hierarchy. You can still create issues above Epics as long it is on top of Epic issue type on the list. There's a bug that when you create a new issue type (Initiative or Legend), it shows up as 2 in the hierarchy level and Epic as 1 and you can't change the order. Just Save Changes and it will work as intended (very confusing I know.)
Great videos, subscribed! please add link to “the other video” you keep mentioning, I’m on my third video trying to find it.
I really need to go back and update these videos. I've been waiting for Atlassian to drop a new feature that will change how all of this works before I invest time into redoing this.
It will be helpful you link those videos you mentioned.
I really do need to go and do that.
Thanks for the video. I need a way to track the time for all of the epics that are under the initiatives.
Why do I have to go watch a video on how to add an Initiative when I clicked on a video called How to add initiatives in Jira?
Honestly. . .I have no idea. This is such an old video. . . I think I'm more organized now. But thanks for the feedback.
Very nie video, I could not find the second part on your page, could you plase share it iin here?
I need to figure out what happened.
How do you create a filter to show the initiatives and all epics, stories and task under it? I’m trying to create a board
Try: issuekey in portfolioChildIssuesOf("INIT-001"). Where you replace INIT-001 with your issue. Please keep in mind this is CASE sensitive.
hi , first thanks for all your amazing videos.
i started to manage the jira issues in my company with no knowledge at all and you save me.
i have a question, i can see that in the advanced roadmap hierarchy its notifying you that this change will affect all plans, what does it mean? if i dont want something above an epic in some projects, will it affect them somehow?
It was great talking to you. Hopefully I answered your questions appropriately. Thanks for the continued support!
@@ApetechTechTutorials in the Advanced Roadmaps hierarchy configuration what matters for the hierarchy to work in the way i want is the numbers(1,2,3) or their position in the hierarchy (from top to bottom) ?
@@mirialexeichick1438 Their position, top to bottom. Make sure you enable the parent link field at the screen level as well.
Will 'iniciative' appear for all the project or just one?
It will be available for any project, but you still have to go to the project settings and add the initiative issue type to that project.
Or, if you have a shared issue type scheme, you just need to add it there.
Does adding an initiative issue type to an existing project cause issues with existing Sprints or reports?
Adding an initiative issue type will be treated as a regular issue type. You'll want to exclude them from your board so that don't impact your sprints and reports.
Hi there. Is it possible to have two level different level names with the same level issue type? in other words, can I have one initiatives under another initiative?
No, that's not possible.
:-/ that's the second video that told me to watch the one before. It's hard to find!
I have followed all the steps, however, on my issue type hierarchy page, I am unable to move Phase (my new issue type) above Epic. As in, Epic is automatically numbered 1, with the new issue type 2 automatically.
How can i make Phase the parent of Epic?
Are you on Jira Premium?
@@ApetechTechTutorials Yes i am
I have this same issue, can you please reply as to why we are seeing 2 for the Initiative???
@@davidkramer275 Same here. Could be be a current bug in Jira? I am using premium but still in my free trail.
Same problem here. Posting in case someone else stumbles across this in the future. Also interestingly, when I click "Advanced Roadmaps hierarchy configuration," instead of what we see in the video, it takes me to "Issue Type Hierarchy." Despite all of those issues it still works. For some reason the numbering is reverse order. So if you've made a new issue type to be above epic and its numbered "2," that's ok! As long as you have it positioned above the Epic level it should work.
Dang Man - you BABBLE on SO MANY TIMES about so many of your previous videos that I keep forgetting what the hell I am trying to solve. A little more focused conversation would be helpful
agh what a waste of time, don't split explanations into multiple videos just to create more content
Hector, I appreciate your comment. The material that was required/needed to cover the topic of this video was covered in the video. Supplemental videos are created to cover other topics that might be related. As you may know, UA-cam favors smaller, specialized topic videos. But, since I see you have some interest, I could cover this entire topic end-to-end in one of my future live streams.