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

Changes to default field configuration applying to new field configurations?

Hi, I feel so confused and hope that someone can help me.

 

What I wanted to do:

-> I wanted to create a specific field configuration for specific issue types

-> For example, I wanted a customized field configuration for bug tickets

What I did:

1. I first created a new field configuration that I wanted to use for bugs and customized it accordingly.

2. In the Configure Field Configuration Scheme, I associated the issue type Bug with the newly created field configuration.

What happened:

-> Any changes that I made to either the new field config or the default field config would apply to the other.

 

Am I missing a step? I feel lost.

Any help would be great!

1 answer

0 votes

Hello @Stefannie Tan,

Welcome to Atlassian Community!

I understand that it might be confusing. I tested here on my local site and I was able to link a field configuration scheme to an issue type, but once the issue type is added to a project, it will follow be linked to the field configuration scheme of the project. 

Each issue type can be associated with one configuration scheme:

  • An issue type can only have one association within a given configuration scheme.
  • If an issue type does not have an association in the scheme, the field configuration associated with the Default entry in the scheme will be used for issues of that type.

Any changes that I made to either the new field config or the default field config would apply to the other.

Can you please let us know more details about what is happening?

If the same field configuration scheme is shared between projects, then if you, for example, set a field as required in the field configuration scheme for Bug, it will affect other projects that have the same scheme. 

Feel free to share screenshots with us, just make sure to hide private information. 

Kind regards,
Angélica

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
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