Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,127
Community Members
 
Community Events
168
Community Groups

Need help with JMWE add-on execution - Prevent new stories added to closed epic

Hi, I have got users adding new stories to EPIC that have already been resolved/Done.

Can someone please help with how we can use the JMWE add-on to achieve this. Thank you ! 

2 answers

1 accepted

0 votes
Answer accepted

Hi Aisha,

this is only possible on Jira Server.

You need to add a "Parent Status Validator" on the Create transition of the subtasks (or shared) workflow, which is accessible in the graphical workflow editor (it starts from the large "dot"), and check the statuses the parent issue must be for the subtasks to be allowed to be created (basically all statuses except Done).

You can also specify a custom error message.

@David Fischer _Appfire_ Hello David. Thank you for the reply.

Does tthis work the same for Epic and story ? I tried and it still allows creating stories under CLOSED epics.

For Epic/Stories, you need to use the "Linked Issues Status Validator" instead, with the "belongs to epic" link type.

@David Fischer _Appfire_ Hi, is the below validator correct ? I added it at the create transition.

All issues linked to the current issue through the is Epic of (from Epic to Stories) link type must be in one of the following statuses: Open or  To Do
The following message will be displayed if validation fails: The Epic is already closed. Select a different Epic

But still doesn't work. 

You need to select the "has Epic (from Story to Epic)" link type instead.

@David Fischer _Appfire_ I changed and still able to create stories under closed epics. Any input on what error I could be making ?

Which version of JMWE for Jira Server are you using?

@David Fischer _Appfire_ I was able to achieve this using workflow properties instead. Anyway Thank you so much for helping out 

Hi Aisha, would you mind sharing your solution here with the community?

@David Fischer _Appfire_ Definitely !

Added the below workflow property at the DONE status (not at the transition).

Property Name: jira.issue.editable

Property value: False

 

Hope this helps :)

Hi @Aisha M

I tried implementing your suggested solution, but was still able to add an open child issue under a closed parent issue. Also, I was able to edit/reopen the closed issue.

Maybe you can explain what the user experience is supposed to be by adding that Property Name and Property Value to the Done Status?

@David Fischer _Appfire_ maybe you can clarify if you have a solution using JMWE? I am using Jira Data Center 8.5.5.

@Gil Vinokoor workflow properties are documented here: https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

And when you tried, did you use "false" as the value (instead of "False" as Aisha improperly typed)?

I have found a traditional way to do it which does not require any addon.

Just by setting workflow properties in the Done status of the Epic workflow hides both the button ("Add Issues to Epic" and "+" button)

 

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

Jira workflow property value - denied

 

For more reference - 

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Apps & Integrations

Apps for Confluence you won't want to miss: RSVP for September's Appy Hours

Calling all collaborators and Confluence users! Our Appy Hours event on September 29th features 4 presenters demoing functionality to superpower Confluence. Don't miss learning about these apps i...

120 views 0 9
Read article

Atlassian Community Events