Require team field to be populated at creation time

Question

Hello Community.  I have a locked custom field called TEAM.  It's used to identify the scrum team that owns the issue and interfaces with Advanced Roadmaps to support sprint capacity planning.  I would like to have this filed be required at creation time but can't figure out the best solution.  Our environment is Data Center and running Jira v8.20.0.  I tried looking at a Validator in the workflow but I don't see an option for 'Field Required Validator'.  As a Jira admin, can I add a new validator option to this screen? Any suggestions on the best option here?

Thanks,

Thayne Munson

Craig Nodwell_7eve9b · Accepted Answer

You could maybe try a post function to test that the field is not null or empty.

Michael Wolfe_7dmwnl · Accepted Answer

I would edit your Project's field configuration, and set that field to "Required".  This would prevent the issue from being created if the field isn't populated:  https://support.atlassian.com/jira-cloud-administration/docs/specify-field-behavior/

PD Sheehan · Accepted Answer

Based on the list of available validators in your screenshot, it looks like you have a fairly vanilla instance of Jira Service Management.

A lot of the more advanced features of Jira workflows are provided by third-party apps from the marketplace. Unfortunately, the good ones are not going to be free.

The three most popular extensions are:

* Jira Misc Workflow Extensions (JMWE)
* Jira Suite Utilities (JSU) 
* Jira Workflow Toolbox (JWT)

JWT is probably the most feature-rich. But I generally prefer JSU for its simplicity and value.

Of course, you could always go the way of Scriptrunner for Jira which has many easy-to-use built-in workflow features as well as the ability to build any sort of rules and automation that are only limited by your imagination and technical skills.

Personally, I would not want to work in an environment without Scriptrunner and JSU.

Sergio del Pino _Decadis AG_ · Accepted Answer

Hi Thayne,

As Peter-Dave mentioned, you can do this with our plugin Jira Workflow Toolbox, which offers the Fields required or changed validator, which lets you validate as many fields as you need, and wether they:

* Have a value set (is required)
* Don't have a value set (must be empty)
* Have changed (must be changed)
* Haven't changed (must not be changed)

Besides, you can also add a customisable error message so the users know why the transition has not been executed.

Below you can see an example of how this validator could look like in your case:

I hope this helps :)

Cheers,

Sergio.

Amir Katz (Outseer) · Accepted Answer

I'm on Jira Cloud now, so I cannot validate my answer. However, IIRC, there is a simple validator, built-in in Jira (meaning no add-ons are needed) that tests that a specific field is not empty.

As other answers have suggested, some add-ons also provide similar validators, with more functionality (e.g. run the validator only if some condition is satisfied), but IMO, using the built-in 'field required' validator is the simplest solution.