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; } } }

When you archive a project with shared configuration settings, will it affect both projects?

Katie Koloj

I am creating a test project for a team, and want to use the same configuration settings as an existing project so they can test the workflow and settings.

Additionally, if I change something in one project, will it also change in the other? (For example, I changed the workflow in Project A, will that automatically update in Project B?

Thank you in advance!

Accepted answers

Max Foerster - K15t

Hi @Katie Koloj ,

Company-managed projects that you create with a shared configuration share system configurations like a workflow, permissions, or field configuration (more details about what exactly is shared by default are available in the documentation). So changes to this configuration will be reflected in both (or more) projects using them. When you archive a project, it will not affect the other project. Both projects are using the same configurations but it's not like you archive the configurations as well. Only the project.

Best, Max

Robert Wen_Cprime_

I believe if you make changes to a workflow that's shared, the changes will apply only to the active project. They won't apply to any project that's archived.

All comments

Max Foerster - K15t

Hi @Katie Koloj ,

Best, Max

Robert Wen_Cprime_

I believe if you make changes to a workflow that's shared, the changes will apply only to the active project. They won't apply to any project that's archived.

Katie Koloj

Thank you Max!

And just to clarify, after you create a project with shared settings, you can unlink the projects? If so, do they retain their settings and just unlink?

Katie Koloj

Thank you!

Max Foerster - K15t

Yes, you can always assign different schemes to the projects, be it a different workflow scheme, permission scheme, or issue type scheme. The configuration is a bit more complicated due to all the different components, but of course, it gives you a lot of flexibility. You can always make the projects completely independent of each other afterward.

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