nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Accepted answers

Veera_zqt9p1

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

All comments

Veera_zqt9p1

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud