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

[Jamie Edmondson]

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!

[Victor Law]

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:

https://confluence.atlassian.com/jirakb/how-to-make-a-field-required-before-closing-the-issue-1236928291.html

Thank you.

[Trudy Claspill]

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.