Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,299,838
Community Members
 
Community Events
165
Community Groups

Require team field to be populated at creation time

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

image.png

6 answers

5 accepted

6 votes
Answer accepted

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/

 

Hi Michael,

I do not have the means to validate that right now (no DC edition in version 8.20 for testing available) but I remember, that in the past the Team field was blocked in the Field Configuration and there wasn't a direct way to make it mandatory via the Field Configuration scheme.

Michael Wolfe Community Leader Mar 24, 2022

@Mathias Richter ,

You are correct.  I see that there is another answer below that seems like it would be a better solution to this limitation.  Hopefully this feature request makes it through the ranks https://jira.atlassian.com/browse/JPOSERVER-2328.

3 votes
Answer accepted
Craig Nodwell Community Leader Mar 23, 2022

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

Craig Nodwell Community Leader Mar 23, 2022

A behavior if you have scriptrunner.

2 votes
Answer accepted

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:

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.

Hi Thayne,

in addition to Peter-Daves answer, I would like to add the following post, that contains the same questions:

Solved: Make Team Field Required (atlassian.com)

ScriptRunner offers a Validator for "Field is required". With this validator, you can achieve your goal but requires an additional add-on.

0 votes
Answer accepted

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.

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:

fieldsRequiredChanged.png

I hope this helps :)

Cheers,

Sergio.

Thanks to everyone for the ideas.  I will check them out. 

Thayne Munson

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you