We have a few issue types: Epic, Story, sub-task, Technical Requirement, Development Task, etc.
By default Hierarchy level is
Can I add
Thanks,
Jenny
Hi @Jenny Chen ,
Since you already have Epic to Story hierarchy, you will automatically have "Epic to Technical Requirement" and "Epic to Development Task" if these are standard issue types.
If you add any standard issue type in hierarchy, it automatically adds all other standard issue types at same level.
Thanks,
Aditya
Hi Aditya,
If I selected Epic as top level, the options for Dev-task and Technical-req cannot be selected ( grey items). Below is the Hierarchy Configuration: I have added the first two rows as attached screenshot: Dev-task <-Development Task and Technical-req <-Technical Requirement. The last three rows were already present as default options. However, I do not have the ability to select 'Epic' when adding new Hierarchy levels. Do I miss anything?
Thanks,
Jenny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jenny Chen ,
You can display hierarchy only from top to bottom levels. Since you have configured "Technical Requirement" and "Development Task" issue types to be above Epic level in your config, you will not be able to filter from Epics to Technical Requirements.
Level above Epics commonly get called things like Initiatives or Legends – though it’s entirely up to you. To add issue types above epics to your plan, you’ll first need to create a new issue type in Jira Software.
Thanks,
Aditya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aditya,
Thanks for checking. I removed frist 2 rows, just keeped the original configration
I am unable to see any issuetype other than Epic, story , sub-task at bottom levels.
Thanks,
Jenny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jenny Chen ,
Here "Story" represents all standard issue types (Bug, Task, Development Task etc.).
If you will create any standard issue type ticket under your epic KTX-1, it will appear on the roadmap here.
Thanks,
Aditya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.