The effect of changing the custom field context from project-specific to global for all projects

[Siska Ayu]

Hi,

I made changes to my custom field configuration as follows:

1. I changed it from being specified for a particular issue type to being applicable to any issue type.
2. I switched the context from being project-specific to global for all projects.

In addition, the custom field is of the "Required" type and the custom field only used in 1 project and 1 field configuration.

After making these changes, I noticed that the updated custom field affected several other field configurations. Even though some screens don't require this custom field, it is still marked as required in other field configurations. As a result, I am unable to create a ticket because this field is mandatory.

I would like to understand why this custom field is affecting multiple field configurations. Additionally, I would appreciate guidance on how to identify which specific field configurations are being impacted by this change.

Thank you.

[Ojase Emmanuval]

Hi @Siska Ayu 

Welcome to the community !!

If you can't find the custom field on the screen of create and still getting field is mandatory error, Please try to use the Find your field function on the issue view to find it.

To find your custom field:

Click on create button

• Click the 3 dots ···  and click Find your field.
• Search for the field you want to find.
• Select the field.

A table with the field’s status, admin-related settings, and details will display information about where you can find the field or why the field isn’t displayed on the issue view. This will probably help you find the root cause of why the error is showing on the screen.

Let me know how it goes.

Thanks,
Ojase