You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello all, and thanks for reading.
We have several customers which use different schemes. Most of them rely on the "default field configuration scheme."
We have a customer who wants the "customer organization" to be filled in automatically for their project, but they must manually enter it for every ticket, regardless of type.
So I did what I thought was the obvious, and created a new field configuration scheme for this customer "Customer ABC Field Scheme" which is still based on the default scheme. I assumed this would copy the default scheme and give it a new name for this customer.
However, when I try to modify the field "Customer Organization" in the "Customer ABC Field Scheme" to prepopulate it, it still leads me to believe it will modify the underlying default scheme, and this data would be applied across the board.
What am I doing wrong? Please help! :)
welcome to Atlassian Community!
I am not sure if I got everything right. In case you have several Jira projects you can define default values for a custom field like "customer organization" using custom field contexts (https://confluence.atlassian.com/adminjiraserver073/configuring-a-custom-field-861253383.html).
As long as the Field Configuration is assigned to a Field Configuration Scheme which is in use by the Jira Project in question it works. In Field Configuration options like Show/Hide and Required/Optional are the ones I am familiar with (according to the explanation in the following article: https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.