How can I block new stories to be created when an epic is already Done/Closed?

[Jerri Chiu]

We want to have a mechanism to stop users from keep adding new bugs/stories into an epic that's already in the Done status. While it doesn't re-open the epic (doesn't changes its Done status), it makes it hard to manage. For example, we may miss the new work completely because the board's filter doesn't include the new issues. We are currently on Jira Server and Jira Cloud instances due to migration.

[Sreenivasaraju P]

Hi @Jerri Chiu ,

You can add below workflow property at done status. 

jira.permission.create.denied   

[Dan Beneke]

@Sreenivasaraju P Does that property need to be added to the workflow applied to the Epic, the story, or both?  We've tried applying it to just the epic and didn't see the expected results.

[Sreenivasaraju P]

you need to apply this property for EPIC work flow at done/closed status.

similar question @

https://community.atlassian.com/t5/Jira-questions/Can-we-restrict-child-creation-under-an-Epic-when-the-Epic-is-in/qaq-p/1744336

[Jerri Chiu]

@Sreenivasaraju P while this may block/hide the create child issue, what if an user creates an issue, and then in the epic link field just fills in the epic link? wouldn't that also add the issue to the epic as well?

[Sreenivasaraju P]

HI @Jerri Chiu ,

Can you try adding below property at done status of epic workflow and check.

Property Key: jira.permission.edit.denied

   Property Value: denied

[Jerri Chiu]

@Sreenivasaraju P Tried that, the "Create issue in epic" button indeed disappeared, but am still able to create child tickets by entering the epic link in the issue during issue creation.

[David Ortiz Bollain]

. 

[David Ortiz Bollain]

This one worked:

Jira workflow property key - jira.permission.create.denied

Jira workflow property value - denied