The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Epic should be required when creating an issue (team-managed project)

Asaad Askar
January 29, 2026

This project is team-managed.

Currently, issues can be created without assigning an Epic.
We would like to enforce that an issue cannot be created without an Epic, similar to how the Summary field is required.

At the moment, this is only handled via automation after creation.
Please let us know if this can be enforced in a team-managed project.

Thank you very much for your help.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

5 votes
Answer accepted
Marc -Devoteam-
Community Champion
January 29, 2026

Hi @Asaad Askar 

Make sure to add the parent field on the work items (not parent) and then for each work item create a validation in the workflow on the create transition.

Asaad Askar
January 29, 2026

Hi @Marc -Devoteam- , thank you for your reply.

Just to confirm: is this also possible in a team-managed project?
As far as I know, team-managed projects do not support workflow validators or create transition validation or I say something wrong?

Thanks a lot for your clarification.

Marc -Devoteam-
Community Champion
January 29, 2026

Hi @Asaad Askar 

This works, I have just tested this.

Asaad Askar
January 29, 2026

Hi @Marc -Devoteam- Marc,
thanks for confirming. I’ve tested this as well and it works perfectly in our team-managed project.

Like Marc -Devoteam- likes this
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events