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

How To Make Component Field Mandatory In Just One Project

Rowan Frankel

Hi,

I am having difficulty following the back-end configuration for making a component field mandatory in just a single project. Making the component field mandatory in all projects is easy (Admin > Issues > Fields > Field Configurations > Component > Required).

I see https://confluence.atlassian.com/display/JIRA/Associating+Field+Behavior+with+Issue+Types , but despite my efforts, the component field is becoming mandatory for all projects.

Can anyone give me a step-by-step guide to making the component field mandatory in just one project without making it mandatory in all projects?

Thanks very much!

Accepted answers

All comments

RambanamP

you have to create sepatare field configuration for each issue type then create field configuration scheme and append to project

it is explained on this document

https://confluence.atlassian.com/display/JIRA/Associating+Field+Behavior+with+Issue+Types

Bharadwaj Jannu

hello Rowan,

you just create a new Field Configuration and make Component/s field required. Now create a new Field Configuration Scheme, add the Field Configuration to it and associate this Scheme to your project that only require Component/s field mandatory.

Kailin Hu

This worked, thanks, @Bharadwaj Jannu! I wish Atlassian's documentation doesn't make Field Configuration and Field Configuration Scheme sound so confusing.

Vlad Gomzyakov

How do you associate a new Field Configuration Scheme with a project? I can't figure out how to do it.

Vlad Gomzyakov

I can't seem to append it to the project because I don't have the Actions menu where I can select to use a different scheme.

Chrisjir Parkin

Disclaimer: these steps apply to my instance of Jira Server.

To associate the Field Config Scheme with your Project:

First, follow the steps outlined above in the answer from Bharadwaj Jannu.
Create a new Field Configuration and add it to a new Field Configuration Scheme.
Then, go to the Project.
Click on the Project Settings (gear icon), lower left.
On the "Project settings" screen, in the section titled "Fields", click on the link to the Scheme.
You'll go to a page that is titled "Fields" and displays the current Field Configuration Scheme for your project. On that page, click on the "Actions (gear icon)" drop-down in the upper-right.
In the resulting drop-down menu, select "Use a different scheme"
You'll go to a page titled "Field Layout Configuration Association" that "allows you to associate a field configuration scheme with the project <your project name>"
In the drop-down menu titled "Scheme" pick the scheme that you created earlier.

Jay_izxrm9

I am on Jira Cloud and worked a treat,

Settings Cog (top right corner next to profile photo)
Select Issue
Field Configurations
Copy existing and rename in a way that makes sense
Open the new copy of the existing field config
Search Component
Click Required
Click Field Config Schemes
Copy existing and rename in a way that makes sense
Click Configure and select the right Field Config created in step 5
Click Projects and find the Project needing Component to be mandatory
Click Project Settings in left hand menu bar
Click Fields
Click the Actions cog on the right hand side above the fields
Click Use a different scheme
Select the newly created scheme

All done ✅

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

jira-administration

required-field

component