How to copy a project?

[marcus]

How to copy a jira project not including data such as issues?

I want to duplicate as a new project, not sharing the configuration.

Regards,

[Melissa Lato]

I have always used this process to move my projects on to the next year and it works fine:

[Micheal Planck]

That's a company-managed project. It does not apply to team-managed projects.

Company-managed projects have to be managed at the administrator level, because changes to their structure affect all projects using that structure.

Team-managed projects can be managed at the project level, because nothing they do affects other projects.

If you want a team-managed project, then you cannot share structure with anything else, not even to start. You have to set up every field by hand.

[Nic Brough -Adaptavist-]

There is no "copy project setup" built into Jira - they expect you to create projects from templates, or use the shared configuration.

There are apps in the marketplace that can do it.

The manual method isn't really a copy either.  You would need to work through all the schemes the project currently uses, copying them to new schemes with new names.  Then create a new project (either from template or with shared schemes) and then reconfigure it to use the new schemes you've just created, and possibly fiddle with some of the other settings.   (This is what the apps in the marketplace do programatically)

[Micheal Planck]

I mean, people know this is nuts, right?

I create some issue types with specific fields and workflows. I want to use that same setup for each of my projects. So I have to re-do by hand every... single... configuration.

How is this not obviously mental?

What is the expected behavior? That you just run all projects in one big Jira database, and filter out the issues for each specific project? That you only ever run one project? That you never use the new Team Managed projects they recommend you use, since the Company managed ones can at least share schemes?

I mean, what do they even think is supposed to happen here?

How do we have software in this day and age that cannot export and import a configuration file? I mean that seriously: how?

[Nic Brough -Adaptavist-]

No, it's not nuts, it's completely sane, and supported.  Just click the "use shared config" button, job done.

Team-managed projects are totally different, and the clue is in the name - they're not intended to be shared, they're configured locally.

[Micheal Planck]

So why do they have to be configured locally by hand every single time?

If Atlassian recognizes the value of sharing a project structure, then why wouldn't all of their products allow sharing a project structure?

If they don't recognize the value, then why did they add it to company-managed?

Also: company-managed projects have a whole host of other issues, which is why they invented team-managed projects: to simplify managing a project.

I actually want my teams to be able to modify their projects as they need; I just don't want to make them do repetitive manual tasks every time they set up a project. I want to be able to kick-start their projects with lessons learned from previous projects.

What part of this is not obvious?

[Nic Brough -Adaptavist-]

Because team-managed projects are supposed to be created and managed by the team - they're supposed to configure them for their usage, not adopt other teams ways of working.

[Micheal Planck]

And each team must start from scratch, and learn everything anew, rather than building on the knowledge of previous teams or even their own previous efforts.

I mean, why would we want to stifle their creativity, right? We could point them in the right direction for managing their projects, by giving them the starting config from the last time they did a project, but it's better if they repeat this work by hand. It'll make them appreciate it more, right?

I'm sorry, but this is just silly. You don't have to defend every stupid flaw in Jira; you don't even have to take my complaints seriously. I'm still paying for it, aren't I? I can't be that upset (I am, actually, I just don't have any alternatives).

[Nic Brough -Adaptavist-]

I'm not defending Jira's team-managed projects, I really do not think they are ready for the enterprise.  The inability to share configurations between projects is one of the things that makes them unusable.  I always recommend company-managed projects to people, so that they can share standards.

[Micheal Planck]

Agreed. It's just such a basic oversight that I can't believe it.

I don't know why my organization decided to use team-managed instead of company-managed; well, other than the fact that the company-managed ones they did start with are a mess because they weren't disciplined enough while managing them.

I'm coming in late and trying to avoid a mess going forward by setting the appropriate examples/guidelines for new projects. And Atlassian is making it harder!

There is a marketplace app I'm going to try, Project Templates for Jira, because its only 10 cents a user, which is an easily acceptable price.

EDIT: That marketplace app only supports company-managed projects. Of course.

And the other apps I have found say this:

We are not able to clone issue layouts because the issue layout is not accessible via REST API. You can vote and comment to let Atlassian know if you need this feature.

So even if you create a company-managed template, and install an app, you still can't push a button to create a new project; you still have to go through and manually copy the issue layouts and automation and who knows what else.

There's literally no way to automate a repetitive task on the computer. Even though my computer swears its 2023.

[Alex Koxaras _Relational_]

Hi @marcus and welcome!!

You can export all your project's issues in a csv file, with all the necessary fields, and then import it on a newly created project. Of course you might have to double check with the data and omit the issue key.

Another way would be to use an app from the marketplace.