Jira Custom Fields property Default vs Optional

[Ratom]

Hi all,

I try to add custom field to multiple projects (currently only 1) but got a problem, because  there are  additional import processes which are failing  because this field is not setup in the current configuration.

I got advice to make this field Optional , did my homework but I don't see this option anywhere.

Though I see Default value configuration  (currently = None).  If I set it to some value from the list  will it serve a replacement for Optional functionality. 

Thanks for advice. My goal to set Custom Field so it will not break any existing imports.
Best
Ratom

[Trudy Claspill · Accepted solution]

Hello @Ratom 

In what types of projects are you using this field?

If you are using it in Company Managed projects there are two ways the field might be marked as Required.

Method 1 is through the Field Configurations used by the projects. That would make the field required at all times during the life of the issue. Refer to this documentation:

https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-field-configurations/

Method 2 is through the Workflow Transitions. When an issue is initially created, and when it transitions from one status to another, it goes through a Workflow Transition. The Workflow Transition may be configured to check that specified fields contain a value. This method is often used when one wants to require a value for a field at a certain point in its lifecycle but not necessarily at all points in its lifecycle. For more information on managing Workflows refer to

https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-workflows/

The above configurations generally can be modified only by Jira Administrators for Company Managed projects, though recently I've seen a new Project Permission that purports to allow delegation of Workflow management to non-Jira Admins. That is a recent change so I have not explored how it works.

If you are using the field in Team Managed projects, then such projects also may have the field as Required during a workflow transition. To make a field required at all times during the life an an issue it would be set to Required in Project Settings > Issues. A Project Administrator for that project can modify both of those configurations.

[Ratom]

Thanks so much Trudy, it's for CMP.

Your comments describe how to make field required, for my case I will try to make it as optional. That's my goal

I also checked configuration inside screens where this field present, there are are no any options only remove/delete.

R

[Trudy Claspill]

In the places where you could set the field to be Required at all times during an issue's lifetime (in Field Configurations) that is the exact same place where you would change it to be optional. 

Did you look at the Field Configuration Schemes for the affected projects? In those you would find how Field Configurations are associated to Issue Types for the affected projects. You would then need to look at the specified Field Configuration for the affected issue type.

Can you share screen images that show the following?

1. the association of the Field Configuration Schemes to the affected project 

2. The details of the Field Configuration Schemes showing the mapping of Issue Types to Field Configurations

3. The details of the field within the Field Configuration that is associated to the affected Issue Type

[Ratom]

Thanks  much Trudy !!!!

I will do it .  For now I just set Default to one of the value from drop down,  Interesting that  I see duplicate values in the  drop down list, looks like Jira allows them?

Task is  getting more complex-).  I need  that field for multiple projects.

While I see in  FIELD CONFIGURATION SCHEMES that   my projects have different  Schemes,

I pick up first one which shared for 2 main projects.

It uses  <Default Field Configuration> and I don't see any options to edit Optional/Non Optoinal yet, will research more.

Best + Happy Holidays

R

[Ratom]

Can see now Required for my field, will check all option to change it.

After clicking on Edit, I don't see option to remove REQUIRED, looks like it's some other place?

[Ratom]

Looks like this Property Required is set only during creating of the Custom Field,

I just played with my sandbox instance and was able to create new field without Required = Y, in this case you can see new option on the right to set it back I think.

[Trudy Claspill]

One additional note, not all fields will have the option to make them Required or Optional. Fields provided out of the box by Jira may not include that option, but all custom fields that you create should included that option.

[Ratom]

Thanks Trudy for great help.
I finally understand where Required YN is located. It's hidden functionality,

Uff, can not imagine that somebody did like this,  I thought I know UX well.

[Ratom]

I changed my Custom Field to Optional and suddenly it broke all projects,

not sure how it can be related.  Have message like below upon Closing the issues.

After setting this field back to Required, this problem disappeared.

[Trudy Claspill]

The Workflow Transition for the transition you were trying to execute (Closing the issue) needs to be examined to see what Rules/Validators/Conditions/Post Functions it includes that may have generated the message.