You can only set epic links for issues on the story level. Please check your hierarchy configuration settings
JIRA is a known project management tool which is really easy to use. Cloud version is really handy and already setup with many things which are mostly required for project management but sometimes it creates problem with the teams which has nothing to do with settings and configuration and that is hierarchy configuration settings. recently JIRA applied an update to its cloud which created a situation were resources are not able to link task with epics because of hierarchy the respective organizations have configured in their JIRA cloud environment. change hierarchy in cloud managed JIRA accounts is a bit tricky and risky as it will be applied to all project and may cause an embarrassed situation for IT resources who are responsible to configuration this change.
Default – Issue Type Hierarchy
Modified – Issue Type Hierarchy
To understand issue type hierarchy, please under given link:
In our case the issue type hierarchy was somehow modified and had task above epic which created this situation and that was only due to a bug in recently released updates by Atlassian. A solution was provided by JIRA support team which is given as under:
Solution!!!
it seems you are running into a known behavior that is being tracked in the bug report (hierarchy configuration settings). To remove this Task from the Hierarchy might affect other projects, so you need to query to see if is there any Epic that the Parent
issuetype = Epic and “Parent Link” is not EMPTY
But you need to ensure that you have the right permissions to check all the projects.
If no epics it’s linked to the task, removing them from the hierarchy will not cause any harm.
In my case no epics was linked to any task so it was easy to remove task from hierarchy to resolve this issue quickly. so I removed issue from the hierarchy and my issue type hierarchy now look like under given:
It resolved my issue, hope it will be helpful for someone else.
