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,448
Community Members
 
Community Events
184
Community Groups

How do I prevent User Stories from being added to a closed Epic?

My team keeps adding new user stories and associated them to closed Epics (which shouldn't be done unless I am aware and can document why).  We have already told the customer these Epics are closed and we either need to associate the user story with a different Epic or consciously reopen the Epic.  Is there a way to prevent users from adding issues to a closed Epic? 

4 answers

Finally, I have found a way to do it.

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

nice, but still able to create subtask under the epic though... :-(

Hello @Klára Zikešová 

Have you found a way by any chance ? 

 

Thanks you 

Hi, well it is a looong time, but I think I did, just cannot remeber how, sorry. But there is a suggestion to make work such property and you can vote here: https://jira.atlassian.com/browse/JRASERVER-10077

Like Joseph HANI likes this

Setting the jira.issue.editable property is not enough. That will prevent you from seeing the option to add a child story to the epic when you are viewing the epic. However, when creating or editing an issue you can still set the Epic Link field to an Epic that is closed.

Per this post

https://community.atlassian.com/t5/Jira-Core-questions/Don-t-allow-choosing-closed-epics/qaq-p/813959

...there is an addon that might help. I haven't looked at the details of the addon yet.

https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions?hosting=datacenter&tab=overview

0 votes
Gary Pasquale
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 29, 2018

Hi @Christina Olson,

Have a look at the advanced workflow properties.

https://confluence.atlassian.com/adminjiraserver073/workflow-properties-861253674.html

You need to use the jira.issue.editable property

Adding a property like this will prevent closed issues being edited. It will affect all issues unless you give epics their own workflow.

Regards,

Gary

@Gary Pasquale I m looking for a solution to the exact same problem. Can you please help me with where to add the above mentioned workflow property (which transition). Also, what group should be selected for the property. Thank you 

0 votes
shetty
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 29, 2018 • edited Mar 18, 2019

Looking for the same

Suggest an answer

Log in or Sign up to answer