How to protect against unlinking a parent issue type?

[Fahim Ahmed]

HI, 

We've recently created a couple of additional issue levels to create more of a Hierarchy Structure. 

These are :

Strategy

Initiative 

Epic 

The Strategy issue type is fixed and unlikely to need to change. We are using Advanced Plans to visualise our Roadmap. 

An issue just arose where someone in error changes one of the issue types of one of the 'Strategy' issue types, thereby unlinking all Child Initiatives linked to it. Thankfully as we are very early in our adoption I was able to identify the unlinked Initiatives and re-link, but keen to understand how I can protect from this happening again. 

1) Is there a way of 'locking' the specific 'Strategy' issue type so that no one else can edit? 

2) In such an instance if someone was to change the issue type, is there a way of 'rolling back' so that the hierarchical parent child links can be resurrected? 

3) Is there any other way I can protect from losing masses of linked parent/child linked data if someone was to make a change to a parent in error? 

[Marc - Devoteam]

Hi @Fahim Ahmed 

You could also think of your structure in Jira itself, related to projects.

I suggest to create multiple projects

Look at it like a Scaled solution

1. create a project for just you Strategy issues, only grant the required people the correct permissions
2. create a project for just you Initiative issues, only grant the required people the correct permissions
3. Team uses their current project.

[John Funk]

Hi Fahim,

Try removing the Issue Type field from the Edit screen for that issue type. If you don't have a separate screen for that, you should create one.