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; } } }

Making a custom field mandatory..what is the correct order of doing things?

Chacha20

I want to make a custom field mandatory for 'Story' issue type. I cannot do it at a project level as there are around 50 or so projects that need the field to be mandated.

The current setup is complex in that there are multiple schemes setup for 'Story' issue type as well as screen schemes etc.

I am confused about what logical order I would follow to make the field mandatory..for example, do I update something in screen schemes or issuetype schemes or workflow schemes etc.

Thank you in advance

Accepted answers

Ste Wright

Hi @Chacha20

It looks like this is a Company-managed Project, based on the fact you mentioned screen schemes - is this correct? I also assume this is internal creation of a Story?

If yes, you need to use Field Configurations / Field Configuration Scheme to do this - which can be applied to all 50 Projects.

Using a Field Configuration you can...

Make custom fields mandatory
Apply the setting to just one Issue Type, whilst keeping the field optional in other Issue Types, using multiple Field Configs in a Field Config Scheme

To find out more, check this help page: https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-field-configurations/

---

If these Projects are Team-managed, you'd have to make the field required on each Project singularly.

You can do this from Project Settings > Issue Types > Story, and opening the field's settings (">"), where you can make a field "Required"

Ste

All comments

Trudy P Claspill

Hello @Chacha20

You have posted your question in the Jira Service Management forum. Are you trying to apply this to Jira Service Management projects or another type of project (Software or Business)?

In addition to that, are the projects where you want the field to be required Company Managed projects or Team Managed projects? You can see that in the information shown on the View all projects page under the Projects menu.

Lastly do you want the field to be required at all times; when trying to initially create the issue and at all times through the issue's life cycle? Or do you want it to be required only sometimes? If only sometimes, what are the conditions for when the field should be required?

Ste Wright

Hi @Chacha20

It looks like this is a Company-managed Project, based on the fact you mentioned screen schemes - is this correct? I also assume this is internal creation of a Story?

If yes, you need to use Field Configurations / Field Configuration Scheme to do this - which can be applied to all 50 Projects.

Using a Field Configuration you can...

Make custom fields mandatory
Apply the setting to just one Issue Type, whilst keeping the field optional in other Issue Types, using multiple Field Configs in a Field Config Scheme

To find out more, check this help page: https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-field-configurations/

---

If these Projects are Team-managed, you'd have to make the field required on each Project singularly.

You can do this from Project Settings > Issue Types > Story, and opening the field's settings (">"), where you can make a field "Required"

Ste

Asha Goyal_0i7i5i

Hello @Chacha20

In agreement with the questions raised by @Trudy P Claspill there are several ways to make the field mandatory:

If you need the field to be madatory at all times, you can do so by making the field required in the field configuration (keep in mind the projects sharing the configuration)

If you need to make field required during a transition, it can be done by field required validator (keep in mind if the workflow is shared by other issuetypes or projects)

If you need to make field mandatory conditionally, it can be done by scriptrunner behaviour

Kindly Accept and vote if this helps

Thanks

Asha

Chacha20

Thank you for your response and yes it is a Team managed projects.

and yes, I do wish the field to be required at all times (creating, editing the issue throughout the life cycle of the issue).

Trudy P Claspill

In your original post you said:

The current setup is complex in that there are multiple schemes setup for 'Story' issue type as well as screen schemes etc.

"Schemes" apply only to Company Managed projects. Given that you have said the projects you want to change are Team Managed projects, then the answer provided by @Ste Wright applies:

---

If these Projects are Team-managed, you'd have to make the field required on each Project singularly.

You can do this from Project Settings > Issue Types > Story, and opening the field's settings (">"), where you can make a field "Required"

Ste

However, that applies only to custom fields created locally within the Team Managed project.

If in your Team Managed projects you are reusing a globally defined Custom Field set up through this screen (https://yourBaseUrl/secure/admin/ViewCustomFields.jspa) you will not be able to make such a field Required within your Team Managed projects.

I was wrong. You can make Global context fields Required in Team Managed Service Management projects. Thanks @Ste Wright for making me retest my findings!

Ste Wright

Just to add, it seems to work for me for both global and local TMP fields

Ste

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-cloud

jira-service-management-cloud

jira-service-management