Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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?



3 answers

1 accepted

0 votes
Answer accepted

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).

Like Muhammad Sharifi likes this
0 votes

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. 

Suggest an answer

Log in or Sign up to answer

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you