Is there a way to prevent an editable field form being empty?

[Filipe Paixao De Lima]

I'm looking for a native way to prevent field from being empty. We have a Squad custom field and the users, when wanting to change squads, usually remove the current squad to then apply the new one. That can lead to two undesirable scenarios:

1: the field remains empty, by human error;

2: the field history will consider the change to/from empty as two changes, so it get confusing when analysing  the squad changing data. 

So I was looking for a way to prevent the field from being empty because that would never be the case, in this specific project. 

[Kris Dewachter · Accepted solution]

Hi @Filipe Paixao De Lima ,

Welcome to the Atlassian Community.

You can use "field configurations" to to make the field required.

In your Jira project go to "Settings" --> "Issues" --> "Fields"

You can have a different field configuration for each issue type in your project, or you can share field configurations over multiple issue types.

See this page for more information on field configurations : https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-field-configurations/

Hope this helps.

Best regards,

Kris

[Filipe Paixao De Lima]

One question about that: if I make the field required, it must be present in the creation screen, right? Or can the issue be created with the required field empty and then an automation populates it (or even manually later)? 

[Kris Dewachter]

Hi @Filipe Paixao De Lima ,

If you use the field configuration, the field will always be required. So yes, it must be present on the creation screen. The automation rule will only run when the issue is actually created.

Will the user be able to select the correct squad when creating the issue?

Best regards,

Kris

[Filipe Paixao De Lima]

Yes. It will be a little change in the process, but doable.

Thank you very much! :)