nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Accepted answers

Trudy P Claspill

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.

All comments

Trudy P Claspill

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/

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

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.

Trudy P 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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud