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 a custom field mandatory on a specific status

Samuel James_hmpnlb

Hi all,

Is there a way to make a custom field mandatory only when the issue is moved to a certain status?

Regards,

Samuel Srun.

Accepted answers

All comments

John Funk

Hi Samuel,

If you have an add-on like JWME or ScriptRunner or JSU - then you an add a validator to the workflow for the transition to the appropriate status for Required Field.

Sarp Egemen

Hi @Samuel James ,

Yes, it is possible to do this natively in Jira.

Let's say you want a text box called "The reason" to be filled whenever an issue is transitioned to the "Impediment" status. I'll provide the exact steps for the scenario above, but you can adapt them to fit your needs:

First, create a custom field of type Text Field (single line) and name it "The reason."
Then, go to Field Configurations and make this field required.
Copy the existing screen for the related issue type (or create a new one) and give it a meaningful name (e.g., "ABC Impediment Transition Screen").
Add the custom field ("The reason") to the newly created screen.
Go to the Workflow settings and open the editor for the relevant workflow (I recommend using the new editor).
Select the Impediment status in the workflow and add a transition rule (click on the lightning bolt icon).
Choose the option to show a screen on transition.
Select the transition (in this case, "Any -> Impediment").
Choose the screen (in this case, "ABC Impediment Transition Screen").
Finally, update and publish the workflow.

This will ensure that when an issue is transitioned to the "Impediment" status, a screen will appear prompting the user to fill out the "The reason" field.

I hope this helps! Feel free to reach out if you have any questions or encounter any issues—I'll do my best to assist!

John Funk

You realize that the field must be populated at the point you create the issue if it is in the Field Configuration, right?

Sarp Egemen

Hi @John Funk

Thanks for pointing out this issue. Indeed, it needs to be populated when the field is set to required.

The default value of "N/A" or "TBD" can be set for "The Reason" custom field upon creation.

An automation can then clear that field after the "Issue Created" action is triggered.

I understand that in this scenario, a more efficient approach might be to use a third-party marketplace app, but I also believe in the true power of Jira.

John Funk

You can’t clear out the value of a required field. Have you actually tried what you are suggesting and had it work?

Nacho Moreno Ortega

Hi Samuel,

I am part of the Decadis Support team and i would like to recommend you our app Jira Workflow Toolbox (Server/Data Center) .

In particular, in the transition to the corresponding status, the validator Fields required or changed checks if fields are set/empty or have/haven't changed on the transition screen.

If you need any assistance with our application, I encourage you to create a ticket on our support portal.

Best regards,

Nacho

John Funk

This would be another good tool to use. :-)

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center