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; } } }

Make Epic Link a required field

Muhammad Alchoum

Hello,

I was looking for a method to make Epic Link field required for some issue types, I couldn't do it on the field configuration because it is locked.

I found this documentation on Jira Software Support: ( How to make Epic Link required on JIRA Software ).

It worked perfectly but now when I want to create a sub-task it says ( A subtask cannot be assigned to an epic ) and doesn't allow me to create because the field is required.

Is there any solution? knowing that i need to make Epic Link required on one issue type only.

Screen Shot 2020-12-31 at 11.04.46 AM.png

Accepted answers

Hana Kučerová

Hi @Muhammad Alchoum ,

welcome to the Atlassian Community!

I believe you need to use workflow scheme with two workflows. The first one for Sub-task issue type, where this validator is not used, and the second one for the other issue types, where this validator is used. Now you are probably using the same workflow for all issue types.

Alexander Bondarev_x6gjf3

Hi, @Muhammad Alchoum !

Welcome to the Community!

Sub-task should not be assigned to an Epic. A subtask is an even more granular decomposition of the work required to complete a story/task, that belongs to Epic throught the Epic Link.

I can recommend you interesting Article about issue hierarchy.

All comments

Hana Kučerová

Hi @Muhammad Alchoum ,

welcome to the Atlassian Community!

Alexander Bondarev_x6gjf3

Hi, @Muhammad Alchoum !

Welcome to the Community!

Sub-task should not be assigned to an Epic. A subtask is an even more granular decomposition of the work required to complete a story/task, that belongs to Epic throught the Epic Link.

I can recommend you interesting Article about issue hierarchy.

Alexander Bondarev_x6gjf3

And of course you should check your workflow configuration - Validators.

If your task/sub-task use the same processes try to add there conditions on Validators, that will ckeck issue type(it depends on your apps).

Muhammad Alchoum

Thank you so much! I will create a new workflow with different validators for sub-tasks. I will let you know if I got anything

Muhammad Alchoum

Thank you so much! I will check the workflow configuration, as you said they both have the same workflow

Sebastiaan Burger

Removing the validation solved my problem

Thank you

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud