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,467,381
Community Members
 
Community Events
177
Community Groups

Prevent adding certain issue type to Issues in Epic

Does anyone know how to prevent users from adding certain issue types to the Issues in Epic section of an Epic?

These guys are using the + button to add issues that do not belong there at all. They don't even have the Epic Link field on any of their screens. When this happens, we have to use a Bulk Modify to clear the Epic Link field. 

Only issuetypes that have an Epic Link field (for example Stories) should be added to the Issues in Epic section. Other issues should be Linked to the Epic instead.

Any pointers on how to use a Validator, Post-function or ScriptRunner Behaviour to prevent this from happening?

1 answer

1 vote

The + sign on the Issues in Epic section brings up a somewhat regular Create screen.

It should be possible in theory to use behaviours to filter the list of issue types (and perhaps even projects).

The challenge I had in my testing was detecting a difference between a normal Create action vs a 'Create issue in epic' action.

If the epic link field is on the screen, you can read it during the initialization phase of the behavior. But if the field isn't there, then you can't

At this point, the only thing I can suggest is creating a listener that watches for unwanted associations and either emails someone or removes those associations and notifies the user.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events