Locking a Jira Story so that it can be cloned but not edited by anyone?

[Katie C]

Hiya,

I've created a Story in Jira with Sub-Tasks, to be used as a template. Idea being that this template will be used to track the process of removing servers, the Story contains all the steps needed to be completed as sub-tasks, and will be cloned as and when a server crops up for removal.

I want to know if it's possible to lock the original story down so no-one can edit it besides myself, but it can still be cloned by others for use. Or if it comes to it, having it locked and having myself clone it as and when requested?

[Manon Soubies-Camy]

Hi Katie,

I don't think there is any native way to lock the original issue edit (and only the original one). You could though hide the issue from other users using Issue security schemes so you'd be the only one to be able to clone it.

I think a better way to implement this would be to use an app like:

• Automation for Jira or Create on transition to trigger subtasks creation;
• Elements to use checklists rather than subtasks.

depending on your needs and whether you're using Jira Cloud or Server.

Hope this helps,

- Manon

[Katie C]

Hi Manon,

Issue Security Schemes might be the way forward for me, the other ideas could work if I had any control over what we use, but I am merely a tiny cog in a big ol' wheel. I'll put those ideas to the powers that be though, could be useful! Thanks :)