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

Your Points Tracker
  • 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
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?
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

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
Ollie Guan Community Leader Nov 25, 2019

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 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
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,157 views 10 14
Read article

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