Can i make field only mandatory for epic?

Jar Lady April 10, 2024

I have child issues which is related to epic. However some fields in epic are mandatory, and my child issues encountered errors in jira automation because they also require these fields. How do i make the fields mandatory only for epic? 

3 answers

1 accepted

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 13, 2024

Hi Lady,

Go to Settings > Issues > Field Configuration Schemes

Find the Scheme your project is using. Click on it to see the details. If there is only one Field Configuration, make a note of that. 

Then go to the Field Configurations menu option. Copy the Field Configuration you noted above. 

Then make the changes to it to make whichever fields you want to be mandatory. 

Then add this new Field Configuration to the Field Configuration Scheme for your project. Make it applicable only for the Epic issue type. 

Jar Lady April 14, 2024

Oh I see that it requires a new field configuration scheme which relies on Jira admin's permission. Noted, thank you!

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 14, 2024

You are welcome!

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 10, 2024

Hello @Jar Lady 

How have the fields been made required?

Are they Required all the time, by being set to Required in the Field Configuration?

Are they required only during a Status change, by using a Validator in the Workflow Transition?

What actions are you executing in the automations for the child issues, where you are getting the problem you think is due to required fields? And what exactly is being reported in the logs of the Automation?

0 votes
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 10, 2024

You would have to create a new field configuration that applies to the child issues, and in it make the fields that should only be mandatory for epics optional. If the required fields are only required as part of a transition then you would need to create a new workflow for your child issues and then remove the condition that makes those fields required.

Jar Lady April 11, 2024

Sorry dun quite get. Do you have sample screenshot?

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 11, 2024

Screenshot of what? The workflow condition or the field configuration? If the fields are always required then the documentation I linked to should have all the information.

Jar Lady April 12, 2024

Screenshot of how I can set it mandatory at Epic and optional for sub-tasks. I can't find the option for that.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.20.10
TAGS
AUG Leaders

Atlassian Community Events