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

Setting Jira custom field to be required for only one Issue Type

Vishal_p33pdz

Hello Community People,

I have a project created in our JIRA environment which has around 15 Issue Types. I have two custom fields which I want to make mandatory & visible only on one of the Issue Type. Can someone help with it ?

I have tried it with Behaviour Settings but it's not working.

Accepted answers

Jorden Van Bogaert

Hi @Vishal

You can set a field required by adding a field configuration and a field configuration scheme. It's the same as with mapping workflows to issue types. You create the field configuration where you mark your specific fields as required, and in the field configuration scheme, you map it to an issue type.

Afterwards, associate the scheme to the project. More info here: https://confluence.atlassian.com/adminjiraserver/specifying-field-behavior-938847255.html

Kind regards
Jorden

All comments

Jorden Van Bogaert

Hi @Vishal

Afterwards, associate the scheme to the project. More info here: https://confluence.atlassian.com/adminjiraserver/specifying-field-behavior-938847255.html

Kind regards
Jorden

Ollie Guan

Hi @Vishal ,

You should set an exclusive field scheme for this special IssueType. Associating an issue type with a different field configuration.

https://confluence.atlassian.com/adminjiraserver084/associating-field-behavior-with-issue-types-979404755.html

Vishal_p33pdz

Hello Jorden,

Sorry I missed this in question itself, actually I have done the same in in field configuration but it's making it require for all the issue type, which I don't want.

I want it to be require for only one issue type & rest all to be hidden & not required.

Jorden Van Bogaert

Hi @Vishal

Have you perhaps made it required in the default field configuration? This will apply to everything that doesn't have a specific association.

Make sure you have a brand new field configuration and field configuration scheme when making a field mandatory.

Vishal_p33pdz

Hi @Jorden Van Bogaert

Yes, I had made default field configuration as required as I didn't want to create more field configuration screen.

I am looking for something like all the issue type should use same screen scheme but using behaviour or something make only those two fields to be available for the one issue type only & remain hidden & not required for rest all.

I am trying to run below server side script using behavior for all the issue type in that project except the one where I want it to be present but it's not working.

def customfield= getFieldById ("customfield_xxxxx")
customfield.setHidden(true);

customfield.setRequired(false);

Vishal_p33pdz

@Ollie Guan thanks for the suggestion, I am actually looking for something where in all my Issue Types to use default screen scheme only ( I don't want to create separate for the said issue type ), I am trying to use behavior & is trying to make the fields visible & required for only one issue type.

Do you have any suggestion ? You may see my conversation with Jorden to know what exactly I am doing.

Cat Camacho

I solved this exact issue-

Go to the "custom fields" screen via Admin settings (under Issues)
Where you can select "Applicable Issue Types", change the selection from "All issue types" to the issue type where the field you are trying to mark required is located. Please note, this solution only works for fields that exist in one issue type only (that I found.)
Then go ahead and mark required as needed.

This should resolve the "requirement" type on other issue types. If the field you want to mark required is in more than one issue type but you only want it required for one issue type, I would suggest creating a duplicate custom field and assign it to the associated issue types and leave that one unmarked as required. Probably not best practice in reporting, etc. since the fields will be the same and unable to be differentiated but it will work.

Hope that helps.

jira settings.png

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server