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

Unable to create sub-task after making custom field required

Jira Subsari

I have created two custom fields which are required for some projects.

Created new project
Created custom screen layout
Created custom field configuration scheme (and assigned it appropriately to the project)
Made two custom fields required

Success - Able to create Epic and prompted for custom field values as expected.

Success - Able to create Story and prompted for custom field value as expected.

Error - Unable to create Sub-task, two fields require value as expected, but also getting this error which is preventing me from creating subtask.

-----------

Epic Link

A subtask cannot be assigned to an epic.

Choose an epic to assign this issue to.

-----------

I have not changed any Epic Link related requirements.

How can I make the two custom fields required and be able to create subtasks?

Current Workaround: I've implemented the logic to requiring custom fields on transition of creating an issue or when completing it, but this requires making the transition requirements for every transition, otherwise I risk fields not being populated all the time. Hoping to find an easier solution.

Accepted answers

All comments

Nic Brough -Adaptavist-

You need two field configurations - one for the top-level issues, the other for subtasks (with the field optional on the sub-task configuration)

Jira Subsari

This is helpful to know. I've implemented this and it solved the issue.

Only follow-up question now is that, using this approach, I cannot make make a field mandatory through field configuration at the sub-task level. I'd have to make it mandatory during transitions, is that correct?

Nic Brough -Adaptavist-

No. You have separated out the field configurations so that issues and sub-tasks behave differently already. You can change the field configuration for sub-tasks to make a field mandatory.

This flag is for every step though. If a field is mandatory, you need to enter it on issue creation and you cannot blank it out at any point. If you want to do "field mandatory during a transition", you need to use "validators" in the workflow to say "must fill this in here"

laura iacob_z3gswq

@Nic Brough -Adaptavist- Hello. I bumped into the same issue. Making a field required for Story makes it required for Sub-task as well. In my project's Field Configuration Scheme I have 2 field configurations: a Default Field configuration where my field is not required - this is for all unmapped issuetypes where Sub-task is included. The second Field configuration is associated with Story and it has my field required. What am I doing wrong? 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