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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Sharing configurations between projects

Having full power for every team to modify their stuff in next-gen project has its pros.

But it also comes with huge cons if you try to manage a larger organization and you want to standardize a few things. It is the same nightmare as it is now with jira service desk: you need to manually copy all the stuff over and over and you can not do one change in one place - you need to do it everywhere.

I really don't see how this could work out well in the end - it is why we try to limit the use of Jira Service Desk and it has the same cause on jira next-gen projects. 

I just googled around - is there any kind of strategy from atlassian if there will be possibilities to share configurations (e.g. issue types, workflows) and so on. basically the same question applies to JSD configs like automation rules - it is just so painfull to manually all this stuff by hand and that in the 21st century....

1 answer

0 votes

Hi @Laurin Stoll ,

Share next-gen project configurations and workflows will coming in 2020.

For teams that want to share next-gen project configurations and best practices, you’ll be able to copy a project, including custom issue types and workflows. Projects will continue to remain independent after you copy them. This will be particularly helpful for teams that want to share next-gen best practices across teams.

But that is still quite bad. Imagine you have 20 teams with a few projects. now you decide to change something. What's the idea behind that - you hire 2 guys that are manually updating all projects?

Like Frank Nock (Chrétien) likes this

Hi @Ollie Guan_携程_ ,

Is it set some deadline for it?

We are right now in the migration phase and it is very actual to have such functionality.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events