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

Importing Project Settings into new Project

John Gerhardy

Hello,

I am new to jira and have the task to set up a new project with the same settings as a working project. Both projects are next gen with simplified workflows. It sounds easy enough, but seems to be more involved that I expected. The new project should have the same issue types (task, finding, issue, bug) with the same context fields as in the other project

Is is possible to somehow copy the setting from one project to new one?

Many thanks

John

Accepted answers

Jack Brickey

You cannot create a new NG project using another NG configuration. Each NG project is unique and standalone. With that said NG is changing daily so keep that in mind if reading this tomorrow. 😂

Ollie Guan

Hi @John Gerhardy ,

Currently not supported, start watching these tickets.

https://jira.atlassian.com/browse/JSWCLOUD-20905

https://jira.atlassian.com/browse/JSWCLOUD-17434

All comments

Jack Brickey

You cannot create a new NG project using another NG configuration. Each NG project is unique and standalone. With that said NG is changing daily so keep that in mind if reading this tomorrow. 😂

Ollie Guan

Hi @John Gerhardy ,

Currently not supported, start watching these tickets.

https://jira.atlassian.com/browse/JSWCLOUD-20905

https://jira.atlassian.com/browse/JSWCLOUD-17434

John Gerhardy

Hello Jack,

thanks for the info. That is a pity, that somehow importing is not possibe, but I can image that you have heard this before. For sure, it is helpful if the team sees the same or similiar structure from one project to the next. Enough said. :-)

You mentioned that things in NG are changing frequently. At the moment, I have not been able to get set the same context fields for the added issue types in the new project to look like the old project. Could the changes be a reason for this?

Example: For the Bug issue type in the old project there is a context field with the symbol

for a drop down like this:

When I add a drop down context field in the new project, it has attributes and if I use the same name (Fix versions) I get an error message !?!

This is the simplest of actions and already an error. It is kind of intimidating. Can you help?

Greetings,

John

John Gerhardy

Hello Ollie,

thanks for the links. They are what I am looking for and I'll keep an eye on them :-)

Kind regards,

John

Jack Brickey

TBH I’m not sure as I don’t really use NG projects much at all. What strikes me odd here is that, based on my understanding, all NG custom fields are specific to the current project. What may be happening here is that you have defined “Fix versions” for one issue type and are now trying to add that filed again for a different issue type rather than simply adding the field to the new issue type. Can you click on each Issuetype in the project settings and check for this field?

John Gerhardy

Hello @Jack Brickey

yes, you are right.

I have added a drop down context field "Fix version" to the task issue type (which was the default issue type after creating the project). The error comes up when I give the drop down context field in the the ne bug issue type.

In the older project, the "fix versions" field is in the task, finding and bug issue types, so I assumed that the context fields belong to the issue type and are local. Is this no longer possible?

Greetings,

John

Welcome!

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

Quick Links

Find more posts tagged with

project

cloud

jira-software

jira-software-cloud

next-gen