how to bypass required field check in automations?

Question

Hi,

We use scriptrunner and jira project automation.

Is there way to bypass required field check in automations ?

Bill Sheboy · Answer

Thanks for that information, Renni.

If you think about this like a data-centric analyst, when a customer asked to make a field required and there was existing data, the analyst would query, "how do you want to handle any currently empty, but now required, fields?"  Otherwise the condition you noted with your original question is created.

As you note the required fields are project by project, a good approach may be to divide and conquer: each project admin can survey their required fields, run a quick JQL search to identify the impacted issues, and then decide next steps.

Renni Verho · Answer

Hi Bill,

In our case there is some fields (variates project by project) which are set as required

eg.  INT project decided to set Fix Version/s required and that is now blocking the update.

Your proposal would be ok in case there is one suitable selection, but often is better that project lead does those updates and that's why idea was to change assignee to project lead.

Based on responses I see we must handle these in another way (maybe manuall mass assigning  to projet lead to make sure fields are filled). Automated handling of these cases in big company would save a lot of time.

Br,

Renni

Bill Sheboy · Answer

Hi, Renni!

In your example, is assignee a required field?  Or...are you noting that:

* fields have been made required after an issue was created (with empty required fields), and...
* during assignee clean-up (for the inactive user) the required fields are blocking the update?

If so, this seems like an opportunity: whenever a field changes to required, search for and update all empty values to set them.  That will keep the information as current as you wish.