nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Asaad Askar

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.

Accepted answers

Marc -Devoteam-

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.

All comments

Marc -Devoteam-

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

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-

Hi @Asaad Askar

This works, I have just tested this.

Asaad Askar

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud