Requiring a field to be populated AFTER creation of an issue?

Jamie Edmondson April 24, 2024

I have a situation in our organization where we need to require a field to be populated, however, we can not require this field to be populated upon the creation of the issue. I am interested in understanding if/how it may be possible to create an issue, and then using automation to require the population of the field before anything else can be done with the issue. Has anyone else run into this situation before, or, does anyone have any suggestions before I dive into trying to figure out how to automate this? Thank you!

2 answers

1 vote
Victor Law
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 24, 2024

Hi @Jamie Edmondson

I recommend configuring the required field under Workflow Validation on the Workflow Transition screen.

Here is an example setting a required field on the Close issue transition:

Thank you.

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 24, 2024

Hello @Jamie Edmondson 

Fields can be made required at all times using the Field Configuration, but that is not what you want.

In Workflow Transitions you can use a Condition or Validator to confirm that a field has a value before an issue can change status.

But there is nothing native that I'm aware of that can make a field required at all times only after the issue has been created.

If you are open to considering third party apps, you might want to look at Adaptavist's Behaviours - ScriptRunner for Jira Cloud. It supports selectively changing field behaviour, though there are some limitations.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events