Changing an Issue Type breaks paren-child linkage

[Dan Spearing]

Greetings,

When I edit a Story level issue type, I can change the Issue's type via the Issue Type dropdown to other types at the Story level, which will not break the parent-child linkage.

However, when I edit a Feature level Issue Type, the dropdown shows Issue types at higher levels which would break the one-level parent-child linkage. I don't want this.

Is there a way to enforce the same restrictions that my Story level issues have (only allow issue type changes to issue types at the same level) to the higher level issue types as well?

Thanks in advance!

[Mikael Sandberg]

The options shown in the dropdown for issue type is based on the issue types associated with the same workflow as the current issue type, it is not based on the hierarchy that you have defined. If you want to limit the options you would have to create a new workflow and associate the issue types that you want to be available to that new workflow.

[Carla Ann Rowland]

If you have Script Runner for jira available you can write a behavior or listener if you are working outside Advanced Roadmaps

[Arkadiusz Wroblewski]

Hello @Dan Spearing 

no, Jira Data Center can’t enforce “issue type can only be changed within the same hierarchy level”.

The Issue Type dropdown is based on what’s in the project’s Issue Type Scheme, not on Advanced Roadmaps levels. So if higher-level types are in the same scheme, they will show up, and changing type is basically a Move operation which can break the one-level parent/child relationship.

What you can do:

Limit “Move issues” permission (that’s what controls type changes).

Separate issue types by scheme/project so the “wrong” types simply aren’t available.

If you need strict rules, use an app-based guardrail (block invalid moves), because Jira won’t do it natively.