Creating a master template to be used to clone for other projects

[MA]

Hello,

My team consists of 3 BA's including myself, we all do the same type of projects so instead of creating the project manually each time, I would like to know what can be done.

Currently, my fellow BA and I have created an excel file with the following field names all populated with information:

• Story
• Issue Key:  Numbered by ourselves
• Release
• Epic
• Description

The goal is to have all the information in the Excel file act as our master or say template for our next properties giving it a name as TRP Master Template

So, how and where do I create this initial template?  Can I upload my file and if so, are there any other fields that need to be filled in?

Once the master template is a project, how can I use this project for other projects, so I want my project to have all the same Epics, releases, stories, descriptions etc.

Each BA will be responsible to create the initial project but point to the template for all the information, they will be the reporter not the person who created the initial project template, and then add in other relevant information.

Also would like for each project to have its own board.

I have been told I am an Administrator and should be able to do the above, however in some documents I see that you need to go into JIRA - Administration and I am not finding this.  Where should I see this information?

I hope this makes sense.

MA

[Clara Belin-Brosseau_Elements]

Hello @MA

As an alternative to an excel file I can suggest trying our app Elements Copy & Sync. You’ll be able to clone issues across projects in bulk for effective project templating.

The idea is to have a master Jira project (the template) that you will clone every time you need to start a new project.

You also have the ability to map workflow status from one project to another.

Don't hesitate to check the documentation, it’s really quick and easy to set up.

The app is for free during 30 days (and it stays free under 10 users).

[Luka Hummel - codefortynine]

Hi MA,

If you change your mind and are willing to use a third-party app, our app Deep Clone for Jira can be an excellent solution for your needs.

How Deep Clone for Jira Can Help:

• Clone Projects: Deep Clone for Jira allows you to clone an entire project, including all issues, their fields, and attachments.
• Clone Issue Hierarchies: You can clone epics, stories, tasks, and sub-tasks while preserving their relationships.
• Preserve Customizations: The app can replicate workflows, boards, and schemes associated with the project.
• Templates for Repeat Projects: You can create a "template" project and use Deep Clone for Jira to replicate it whenever needed.
• Flexible and Easy to Use: The user-friendly interface ensures that administrators and team members can handle cloning with ease.

With Deep Clone for Jira, you don't need to manually recreate projects or rely on Excel files. Everything is automated and ensures consistency across all cloned projects.

[Klaudia Schön_Deviniti_]

Hi @MA

If you are looking for a more user-friendly tool than i.e. Automation, I'd like to recommend you the Issue Templates for Jira app provided by Deviniti. This app allows you to prepare even complex structure as a template (epic-stories-sub-tasks) and then, apply this to a newly creating issue. Please refer to this page: https://deviniti.com/support/product/issue-templates-cloud/ to read about this app a bit more, watch a video or access video tutorial. I'm sure you will find it useful.

Best regards, Klaudia

[Trudy Claspill]

Hello @MA 

Jira does not have a built in solution for "cloning" a project including all the issues in it, Release Versions, board, etc.

Jira provides the capability to create a new project from an input file that contains information about issues that you want to automatically create in the project. This does not include ensuring that it otherwise has the same configuration as other projects; i.e. issue types, screens, workflows. And it does not include configuring a board for the project.

Are you willing to consider a third party app that provides a solution for this?

Also, what type of project are you intending to use? Would it be a Software or Business project? Would it be Company Managed or Team Managed?

I have been told I am an Administrator and should be able to do the above, however in some documents I see that you need to go into JIRA - Administration and I am not finding this.  Where should I see this information?

If you are a Jira Product Administrator then you should see a gear icon near your Avatar in the upper right corner. If you click on that, as a Jira Product Administrator you should see options like System, Projects, Issues, and more. If you don't see such options, then you are not a Jira Product Administrator.

[Trudy Claspill]

Also, note this is a public forum, so you may want to change your profile to not show your email address.

[MA]

Hello,

I prefer no add on's as we are asked to use the package as is.

Seems I am an Administrator as in the gear I see - System,products,projects,issues and Apps

Where can I go to remove my email address from appearing in forums?

Thank you,

MA

[MA]

Also, this will be a Software - Company Managed using the SCRUM template.

[MA]

Seems I may have found where to update my public profile I changes it to MA previously it was my email address.

[Trudy Claspill]

Thank you for the additional information.

Given that the project type will be Company Managed Software, if the people that are creating the projects are all Jira Administrators, and if it is desirable that the projects all use the same issue types, screens, workflows, permissions, etc., then they can leverage the option to create the projects using the Share settings option.

When that box is checked you can then specify another Company Managed project for which you want to share the configuration settings. This means that the new project uses the exact same schemes and scheme elements as the specified project, not copies of those. If changes are made to those then all projects that share them are affected.

That option does not copy the configuration of the project's agile board. That will have to be reset manually in each new project.

It also doesn't copy project specific information, like issues, components, release versions, or users/groups assigned to project roles.

You could use the Import option to import the issues from a source file into the project. However, the "new" version of import guides you to create a new project at the same time, but bypasses the option that would let you select the above Share settings option.

A Jira Administrator can access System > External System Import, and then select the Switch to old experience option to access the path that supports importing data from an input file into an existing project.

Importing issues in that manner does not solve any requirements related to board configuration or assigning user/groups to project roles.

Another alternative would be to use Automation For Jira feature to create rule(s) that would clone all the issues from an existing "template" project into a newly created project. That can be a fairly complex endeavor itself, depending on the number of issues in the template project.

Using A4J for issue cloning does not solve any requirements related to board configuration or assigning user/groups to project roles.