Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,046
Community Members
 
Community Events
176
Community Groups

Subsequent assignment of different issue type screen scheme

Edited

Hi all, can anyone tell me if this is problematic?

In a project with an issue type screen scheme A a lot of issues are already produced.

Now the need has arisen to assign a new issue type screen scheme B to that project subsequently, because one of the screen schemes within the issue type screen scheme has been adjusted and is only applicable to this single project.

Is that possible or does it produce problems?

1 answer

1 accepted

0 votes
Answer accepted
John Funk Community Leader Jul 26, 2022

Hi Anette,

It shouldn't pose a problem - other then there might be different fields show up on the screen. But no data will be lost. 

Hi John,

thanks for reply, it's good to know!

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events