nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Accepted answers

All comments

Sreenivasaraju P

Hi @Jerri Chiu ,

You can add below workflow property at done status.

jira.permission.create.denied

workflow property.PNG

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.

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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server