Find out how a field was set to required

[Ashley Honeycutt]

Hi all,

I received an incident that a user could not clone an issue as expected. The error message suggested that a field was required to create the new issue but the current issue did not have a value for that field.

This project uses our default field configuration. On a closer look, several custom fields that are specifically used only in certain projects are set to required.

I looked at the audit log but it looks like this type of event is not captured.

Is there any other way to see how/when this was done?

[John Funk]

Hi Ashley,

I am not aware of a way to see the changes for anything not in the audit logs.

[Ana Vitória Selista]

Hi Ashley,

You can find error logs in the jira-logs file, I think.

In your case, I would recommend creating a copy of this field configuration, reviewing the required fields, and applying the copy only to your project. This way, you avoid setting a field as required when it might not be present on the screen.

This issue could also be caused by a validator in the workflow, as fields can be set as required at the moment of creation. It’s worth checking the workflow settings to confirm if any validators are enforcing this requirement.