I have an Epic created in my JIRA project, and then I clicked "Add a child issue", and chose the type "Story" from drop down list and filled in other fields, then tried to save the issue (story), however it gave me the following error message
"You can only set epic links for issues on the Story level. Please check your hierarchy configuration settings."
I have issue type hierarchy setup as following:
Based-on the setting, the user story can be a child of epic. Not sure why I still got the error message and cannot create it as Child?
Thanks
Hello @Ivan Yuan
Welcome to the Atlassian community!
I suspect that you issue hierarchy is incorrect.
Can you show us the complete issue hierarchy?
Also, can you tell us which issue type are selected based on the icons shown in you image, to the right of Epic?
In that field in the issue hierarchy you should be selecting the issue types that you want to be equivalent to Epics. Based on the icons I think you might have added the Story (and maybe the Bug) issue types into that field which is telling Jira you want them to be equivalent to Epics. That is not a supported configuration.
The native issue hierarchy in the Standard version of Jira is:
Epic
|-- standard issue types: Story, Bug, Task, etc.
|-- subtask issue types
You can create additional issue types at the Standard and Subtask levels, but not at the Epic level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ivan Yuan
Welcome to Atlassian community!
Can you please check and verify the hierarchy of the issue types within the project and confirm?
A similar question was raised sometime ago and you can refer to the alternative/ solution mentioned: https://community.atlassian.com/t5/Jira-Software-questions/Can-only-create-user-stories-in-epics/qaq-p/2066040
Hope this helps.
Thanks,
Vamsi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vamsi Kandala Thank you for your instant reply. I think I have the types Hierarchy configured. Please see my original post that attached with screenshot of hierarchy configuration. I believe it is correct, can you please help to check for me?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ivan Yuan
Looks like all the issue types are in the same level and so it is not allowing you to create Story under Epic. Can you try removing Story issue type from that list under 'Jira Issue Types' and check?
Thanks,
Vamsi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Vamsi Kandala Thank you! It works by removing Story from the hierarchy list. Now it looks as below. What is real relationship of the issue types in below hierarchy definition. Does it mean "Epic", "Bug", "Feature" can be a child of "Epic"? Perhaps I'm confused about the definition
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ivan Yuan
Glad that it works now.
The column under 'Level Name' defines the hierarchy order. So, the hierarchy follows as 'Epic -> Story - Sub-Task'.
The column under 'Jira Issue Types' defines the similar issue types where the hierarchy level should be the same as that of the issue type under 'Level Name'. In your case, right now, it is defined that the issue types 'Epic', 'Bug' and 'Feature' are of the same level. So, you CANNOT create a 'Bug' or 'Feature' ticket under 'Epic'. If you want to, then you will have to remove that issue type from this list.
Hope I am able to clear your confusion. Feel free to ask if you have questions.
Thanks,
Vamsi
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.
Online 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.