shared configuration vs. template in a new project

[sureshksuresh95]

Please clarify I am correct ! 

(i). I understand that 'shared configuration' option available only for  CLASSIC projects; and it inherits, configures the original project schemes to the new one!

(ii) NextGen projects are created without any concept of schemes (except Jira itself assigning few default schemes like - security // notification etc..

thanks.

[Veera · Accepted solution]

You are right. 

Next-gen projects doesn't have share config. You may find more details on Next-gen in the blog post: Everything you want to know about next-gen projects in Jira Cloud

[Ste Wright]

There is some upcoming changes in 2020 though to allow for duplication of another, existing Next-Gen's configuration during project creation.

Check out what is coming up on the Public Roadmap.

Ste

[sureshksuresh95]

Thanks!!

[John Funk]

@Ste Wright  - I don't think that Roadmap means shared as in what shared means in Classic projects. Specifically, it says Copy configurations and workflows. But the copied one will remain independent from the original one that was copied. So there is not a single shared workflow but still several different ones. Changing one would not change the others. If I am reading all of that correctly.  :-)

[Ste Wright]

Hi @John Funk

But this does replicate the base function of the "share configuration" option during Classic project creation.

I see this to mean the new project will replicate the configuration of the existing project, rather than share it. That means it will remain independent and is flexible to change without disturbing other teams - instead of shared configuration, where all teams are using one workflow so a change affects them all.

^ I think we might have crossed understanding on "share configuration at creation" and "shared configuration" - I've tweaked my response above :)

Ste

[John Funk]

@Ste Wright  - Yep, we are on the same track now.  :-)