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


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?



2 answers

1 accepted

0 votes
Accepted answer

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.

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

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


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?

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,637 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you