Cant use Issue type hierarchy as configured

[JAGE]

I have configured the following Issue type hierarchy





But trying to create a feature, under the epic level, gives me an error. The error is not very descriptive.

[JAGE]

Thank you for taking the time to reply, Walter.

For clarifications sake, the Epic is a new level which I created and the "Story" is the "hardcoded"  Epic which I renamed and swapped the icons between.

The weird thing is that in the PROD domain this works as intended.
Can't seem identify what is different between these two configurations, which would cause the sandbox domain to be broken.

[Walter Buggenhout]

Hi @JAGE,

A bit of an educated guess, to be honest, but I think this may be related to having moved Epic to a higher level in your issue hierarchy.

If I look at my environments, I don't see the Add child issue option in any hierarchy level but Epic. In the past, child issues of epics were linked via the Epic Link field, which is now deprecated but not entirely phased out yet across the entire feature set in Jira. Epics expect the story level issues as children and that is what the - indeed not very clear - error message is trying to say.

I'm afraid it won't be possible yet to add child issues to epic in a modified hierarchy like you have configured it. Adding child issues to a parent epic would work by filling out that same epic as a parent in the parent field on your feature issue instead.

Hope this helps! 

[Walter Buggenhout]

This was what I was assuming indeed, @JAGE, as there is no way to literally move epic to a different level.

For clarifications sake, the Epic is a new level which I created and the "Story" is the "hardcoded"  Epic which I renamed and swapped the icons between.

I am not sure how old your sandbox is, but I can imagine some differences may occur if it hasn't been refreshed for some time. Depending on what changes you have set up on your sandbox that are not in production yet, you might see if removing it and spinning up a new one resolves the issue. Or, alternatively, you could raise a support request with Atlassian support to investigate and confirm the root cause of the issue directly inside your site.

[JAGE]

Awesome, thanks for the reply.
Will raise a ticket since the sandbox is not that old.