Sharing configurations between projects

[Laurin Stoll]

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....

[Ollie Guan]

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.

https://www.atlassian.com/software/jira/whats-new/next-gen#result-3d7aca64

[Laurin Stoll]

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?

[Girts Mazais]

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.