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

Make a field required for one project but not for another

Graeme Fidler

I want to make the Components field a required field on one project, but not a required field on another project.

E.g. When creating an Issue in "Project A", I want the Component field to be a mandatory field, but when creating an Issue in "Project B" I do not want Component field to be mandatory or infact displayed.

How do I do this? At the moment I only seem to be able to globally control if the field is mandatory for all projects.

Accepted answers

RambanamP

you can make component field mandatory in two ways

1. you can make mandatory on field configuration, go to the field configutation which you configured for that issue type on which you want to make mandatory then search for component field and click on rquired option

check here for more information(Making a field required or optional)

https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour

another one is by configuring field required validator on required transition

check this

https://jsutil.atlassian.net/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Validators

All comments

RambanamP

you can make component field mandatory in two ways

check here for more information(Making a field required or optional)

https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour

another one is by configuring field required validator on required transition

check this

https://jsutil.atlassian.net/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Validators

Udo Brand

You would need to have two field configurations (one with component mandatory and one optional) see Rambanans first link. Then add those field configuration to the field configuration schemes in those projects (they need to use different ones)

Jennifer Zou

Yes, you need to create two field configurations.

Vlad Gomzyakov

I can't figure out what to do when I created the second field configuration. How do I assign it to the project?

Oksana_Veretiuk

See section Associating a field configuration scheme with a project

The whole flow is:

1. Create to "Jira Settings" > Issues > Fields section > Fields Configarations

2. There will be Default Fields Configaration created and we need to create the one with the field we want to be required > click on "Add Field Configuration" > Name it (my is "Required"

3. Click on the "Required" next to the field you want to be required (it will get "Required" next to its name after this.

4. Go to "View Field Configuration Schemes" (on the same page on the blue panel) > "Add Filed Configuration scheme"

5. Go to the project you want this field to be required > Project Settings > Fields > Actions > Use a Different scheme > Select the scheme created in the previous step > Associate

6. Field gets assosiated and required while creating Bug for this Test project. And not required for the other projects

7. To add Issue types you want your field to be required > clicl "Actions" > "Edit Fields" > click "Assosicate an issue type with a field configuration" > select the issue type and your field configuration

Note that when you create a new project you need to associate it again as by default Default Configuration is applied.

jessica_souza

Great detail, thank you

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration