Prevent issues from being assigned to Closed Epics or Initiatives

Barry Hedgcoth

Hi,

As a Jira administrator responsible for Jira hygiene, I need to ensure stories and other issues are not assigned to Closed Epics and Epics are assigned to Closed Initiatives. So I can ensure I have proper hygiene and accurate reporting. 

Background: Stories maybe misassigned epic names. Stories may also be cloned without the epic being updated. This causes constant hygiene issues and is cumbersome to maintain for a large team / organization. 

Is there a way to configure the workflow to prevent issues being assigned to an Epic/Initiative that's closed? Or is there an alternative "Closed" status that would allow this? 

 

Thank you,

Barry

Miklos Tix

Hi @Barry Hedgcoth

I think you can use workflow properties but only in case you restrict all edit on the epics that are in Closed status.

You can use the jira.issue.editable = false on the Closed status and users won't be able to add new issue to closed Epics and they won't be able to edit closed epics either.

Hope this helps!