Do not allow to clone or create issue when an epic is Done

[steff]

Hi there!

I am trying to find a solution to prohibit creating ( or Cloning) issues when epic is done.

I have read some articles that talk about it and advice to set a permission property in Done status of the workflow like  jira.permission.create.denied or edit.denied ...But it's not working for me.

So If anyone has any ideas I would be grateful! Maybe i can use scriptrunner for it? 

Thanks!

[Calvin · Accepted solution]

HI mate, I tried this in my system and it seems to work okay:

jira.permission.createclone.denied = true

This is set as a property on the "Done" status of the workflow

The clone button just totally disappears for me.

[steff]

Hi Calvin, thanks for your answer.

that's not really what i need in fact. but i think i did not explain well my needs !

Let me explain.

I have an Epic that contains  issues (stories, tasks whatever..). my epic is done/closed and don't want that people clone one of the child issue that add a new child to my epic.

I mean that when an epic is closed it should be frozen. nobody can't add/clone child to it.

anyway thanks for the tips i didn't know the "createclone" permission ;)

[Calvin]

Hi steff. Thanks for confirming.

This is just an idea so might not work so if possible I'd try this in a test environment first to see if it does what you like.

But in the "create" transistion of the stories/tasks, you can add a validator which can check the "parent" status.

This looks like it won't block you from creating, but will block you from cloning or adding it to a parent thats already "done".

The error is not great however.

I would say its a bit unsafe. You might find it better to create an automation to add a comment to the user when they do this telling them not to. Which would allow the user to fix up their issue instead of you having to enforce it.

[steff]

Thanks Calvin!

This is an interesting lead. I'll keep looking.

As soon as I find a good solution, I'll post it!