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

Is it possible to make field mandatory for specific projects only when screens are shared

Manju Nambiar

Hello,

One of our JIRA users wants to be make certain fields mandatory only for her projects. However, other projects also share the same issue screens. Hence, making the fields mandatory will affect other projects as well. Other than creating new screens for the requested projects, is there any other way?

Thanks,

Manju

Accepted answers

Nic Brough -Adaptavist-

That is exactly what the field configuration schemes are for (mandatory has nothing to do with screens - all screens do is list fields to be presented)

You need to divide your field configuration schemes into two - one for each group of projects.

All comments

Nic Brough -Adaptavist-

That is exactly what the field configuration schemes are for (mandatory has nothing to do with screens - all screens do is list fields to be presented)

You need to divide your field configuration schemes into two - one for each group of projects.

Manju Nambiar

I was so hoping this could be acheived without having to touch the field configuration schemes.

Nic Brough -Adaptavist-

That's what the schemes are for. How else would you do it? (Well, without rewriting the whole screen and scheme setup)

sap1

hey,

if the fields itself are shared by a number of screeens then is there a way to make it required for one project while all the others remain unaffected?

Tim Theis

You can add a validator to the WF to enforce the field to be required (but this assumes that your projects have unique WFs).

Muhammad Akram Sharifi_y6l7bk

I dont know if still someone has this issue but posting it here just for future use may it will help someone

in order to make required a field where its using the same field configuration scheme with other project the best practice is to make the field required on the workflow transitions.

First add the Field to the View, Edit and Create screen of the project issue type and then make it required to the Create transition of the workflow.