Required field only working on create not update of issue

[Derek Knudsen]

I wanted to change a field to be required.  I have my custom field setup in it's field configuration to be required.  That field configuration is mapped to the Bug type.  When I create a new Bug the field is required but when I edit the field it is not.  Is this expected behavior?  The field does have a context as it is a multi-select field.

[Trudy Claspill · Accepted solution]

Hello @Derek Knudsen 

Just for clarity, can you tell us if you are working with a Company Managed project or a Team Managed project?

And when you say the required field is not working during editing, do you mean that you can clear the field of an existing issue?

[Derek Knudsen]

Sorry for the delay @Trudy Claspill 

All our projects are company managed.

For clarification when I create a new issue it is showing up as required but for existing Bugs that have no value (ones that existed before we introduced this field) when I open them and edit any field it is not prompting that the field must be filled out.  If I open a ticket that does have it set and try and remove it then it does prompt me.  

[Trudy Claspill]

Thank you for the clarification.

That is working as designed, unfortunately.

With the new Issue View there is no longer a separate Edit Issue screen that allows you to edit multiple fields in one go and click the save button, then validate the fields. The Inline Editing option allows you to edit each field separately and validates only the edited field.

The only method I can think of that might be a work around is to instead use a self-reflecting transition in the workflow with a Transition screen that presents all the fields you want to allow to be editing, and allow editing only through the use of that self-reflecting transition. 

I think I must be missing a simpler solution, so I've posted the question to other community leaders to review.

[Trudy Claspill]

@Derek Knudsen 

I have confirmed with the Atlassian team that the product is working as expected.

The self-reflecting transitions is the only method for "enforcing" a newly Required field on pre-existing issues in the event of any field being edited for that issue.

You can execute a search for issues where the newly Required field is empty and using bulk change, automation, or manual follow up to make sure the field gets filled in for the pre-existing issues.

[Derek Knudsen]

Thanks @Trudy Claspill I was afraid this might be the case.  I will do the bulk update just to get the field set.  Thanks for your help!