Hi Community,
I want to create a custom level of hierarchy above the Portfolio Epic in JIRA data center.
My use-case is:
Here, I only want to add the new level in a specific project, not disturbing already existing Parent-Child flow (i.e. Epic > Feature > Task > Sub-task) with the above use-case.
I also followed the below articles and video for reference but I need to understand how I can configure a new hierarchy level above epic for a specific project in JIRA data center instance:
https://confluence.atlassian.com/adminjiraserver/configuring-custom-field-contexts-1047552717.html
https://www.youtube.com/watch?v=M1TvgkwGnLE
Please guide further with detailed explanation on how to configure a custom hierarchy level above epic in Jira datancenter.
Thanks
Basically, if you only want to add a layer above the layer that is currently the highest, it won't affect your existing data or Plans.
It would only affect it in the way that in a Plan, you would now have the option to select issues from "Epic+1-layer > sub-task" instead of "Epic-layer > sub-task".
Do you have a test/acceptance environment you could play around with to make this change?
Also:
- Which version of Jira Data Center are you using?
- As I understand, you already have a custom hierarchy (the 'Feature' issue type below Epic). Is that correct? Also, did you use the 'Terminology' feature in Jira Admin System Settings to apply any changes already?
Hi @Hans Polder
Thank you for your message.
I have JIRA data center QA environment with version 9.4.20.
I am able to create a new level of hierarchy above Epic as Initiative and linked it with an issue type as Intake Request.
Later, I looked for "Terminology" option in Jira Admin System Settings and could see that Sprint(s) and Epic(s) are defined there. But I would like to ask, is there any impact of Terminology option when configuring a custom Hierarchy Level?
After creating a new custom level as Initiative and placing it above Epic, I am able to link it with a specific project and it's Issue Type scheme, Issue Type Screen scheme, etc.
Now, I have further concerns as below:
Could you please guide me where exactly I am making the mistake when creating a new level as Initiative above the Epic and then using it in specific project as I am not able to show the values of custom fields (created with Initiative) on the Dashboard?
Please let me know if you need any additional details.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thanks for your elaborate reply!
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.