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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Make a field required for one project but not for another

I want to make the Components field a required field on one project, but not a required field on another project.

E.g. When creating an Issue in "Project A", I want the Component field to be a mandatory field, but when creating an Issue in "Project B" I do not want Component field to be mandatory or infact displayed.

How do I do this? At the moment I only seem to be able to globally control if the field is mandatory for all projects.

2 answers

1 accepted

0 votes
Answer accepted

you can make component field mandatory in two ways

1. you can make mandatory on field configuration, go to the field configutation which you configured for that issue type on which you want to make mandatory then search for component field and click on rquired option

check here for more information(Making a field required or optional)

https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour

another one is by configuring field required validator on required transition

check this

https://jsutil.atlassian.net/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Validators

You would need to have two field configurations (one with component mandatory and one optional) see Rambanans first link. Then add those field configuration to the field configuration schemes in those projects (they need to use different ones)

Like Paula Hidalgo likes this

Yes, you need to create two field configurations.

I can't figure out what to do when I created the second field configuration. How do I assign it to the project?


See section Associating a field configuration scheme with a project

The whole flow is:

1. Create to "Jira Settings" > Issues > Fields section > Fields Configarations 

2. There will be Default Fields Configaration created and we need to create the one with the field we want to be required > click on "Add Field Configuration" > Name it (my is "Required"

Screen_1.png

3. Click on the "Required" next to the field you want to be required (it will get "Required" next to its name after this.

4. Go to "View Field Configuration Schemes" (on the same page on the blue panel) > "Add Filed Configuration scheme"

5. Go to the project you want this field to be required > Project Settings > Fields > Actions > Use a Different scheme > Select the scheme created in the previous step > Associate

Screenshot_1.png

6. Field gets assosiated and required while creating Bug for this Test project. And not required for the other projects

Screenshot_2.png

7. To add Issue types you want your field to be required > clicl "Actions" > "Edit Fields" > click "Assosicate an issue type with a field configuration" > select the issue type and your field configuration 

Screenshot_3.png


Note that when you create a new project you need to associate it again as by default Default Configuration is applied.

Like # people like this

Great detail, thank you

Suggest an answer

Log in or Sign up to answer
TAGS

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