Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,556,428
Community Members
 
Community Events
184
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
David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 01, 2018

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.

David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 08, 2019

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. 

David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 08, 2019

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 ?

David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 08, 2019

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 

David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 09, 2019

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.

David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 05, 2021

@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
AUG Leaders

Atlassian Community Events