Jira Automation - Prevent Story being created uder Feature

[JIRA sys-admins]

Is it possible to prevent Story, Task, Sub-task being created under Feature using Jira Automation?

I want only Epic can be created under Feature and Story can created under Epic, so we want to maintain the following hirerchay:

Feature

||

Epic

||

Story

||

Sub-task

[Mark Segall]

Hi @JIRA sys-admins - You should be able to enforce hierarchy in the Issue Type Hierarchy settings here:

https://YOURINSTANCE.atlassian.net/jira/settings/issues/issue-hierarchy

Once you set Feature above Epic, Only Epics will be able to set Feature as Parent Link.

Additionally, you can take the belt and suspenders approach and remove the Parent Link field from Story, Bug, and Task screens. 

[JIRA sys-admins]

@Mark Segall  i see the following msg:

Changes to the hierarchy configuration will only apply to plans in Advanced Roadmaps.

However, this applies to the whole site, we only want the hierarchy to be only applied/restricted on single project?

[Mark Segall]

Unfortunately, there's no in between (at least not natively). My recommendation would be to establish some site-wide governance with your organization to align upon an issue type hierarchy that works for all.

If that's not an option, you may be able to do some magic with a marketplace app like scriptrunner and use a scriptrunner validator to enforce the hierarchy, but the tactical behind setting that up is beyond my skill set.