How to use a "company based" project as a project patern?

[Marcelo Canaparro]

I created a "company based" project and made many automations and configurations and I want to make it a pattern for other projects but I couldn't figure out how to easylly copy the skeleton to other projects.

[W_Diehl _Litew8 GmbH_ · Accepted solution]

Hi @Marcelo Canaparro

great question, let's dive into it. 

Using Projects as Pattern

Sadly, like others have pointed out, the only available option natively is to create new projects with the 'Share settings with existing project' check box. But this approach is very limited and will only create the project with shared configuration schemes (workflow, issue type scheme...) but will not recreate project elements, automation rules and issue structures. 

Cross project automation rules

When it comes to automation rules, the native approach to use automation rules among multiple projects would be changing the scope to 'global' or 'multiple projects'. Note: Atlassian restricts the amount of cross project usage based on which Jira plan (Free/Standard/Premium/Enterprise) you are using. 

In many cases, putting the automation rule on global scope is too much, and 'Multiple Projects' setting comes with the limitation of having to manually add the new projects after creation. 

Third party solution

Since you are not alone in the need to reuse project as pattern/template for new projects and many are stuck with the nativ limitations mentioned above, we've built an marketplace addon that aims to tackle as much as possible for an easy project setup.

Projects Template for Jira

The app allows to built custom project templates based on existing projects or predefined elements. 

Reuse schemes, but additionally most of all the other project elements as well if intended. (Components, Version, project category, Issues with hierachy and links, project role actors, project- lead/description/url and much more)

Sadly when it comes to automation rules, Atlassian has only recently started providing API support but not yet sufficient enough to clone rules or even add projects in the rule's scope. The only option that comes to mind is, creating a custom project template with a specific project category, setting the scope to global and use an if condition directly after the trigger to see if the project that the automation rule was triggered on matches the project category. 

Hopefully Atlassian soon provides more APIs for automation rules, so we can at least include it in the project templates of the app.

Feel free to follow up if you have any questions @Marcelo Canaparro 

[John Funk]

Hi @W_Diehl _Litew8 GmbH_  - Is this an AI generated answer?

[W_Diehl _Litew8 GmbH_]

Hi @John Funk

Thanks for the compliment, I guess that means my non-native English is somewhat alright? But no, just me writing my thoughts to the questions from my experience working on the topic and app.

What makes you think that way?

[John Funk]

Ah you're right - sorry for the confusion. I was mainly looking at the formatting but also that the answers didn't really line up. But then I saw the add for the app nestled in there. Are you associated with this app? 

[W_Diehl _Litew8 GmbH_]

For sure, as mentioned in my initial answer.

we've built an marketplace addon that aims to tackle as much as possible for an easy project setup.

Projects Template for Jira

[shib saha · Accepted solution]

Hi @Marcelo Canaparro , Once you have created a company managed project and configured it and make it ready to be used as a template for next phase of project. There are two separate things one is scheme of the project and another one is the automation rule.

1. For all the schemes to be copied to another project, at the time of project creation you will see an option 'Share settings with an existing project', tik this box and search for the existing project in the search box and select, it will copy all the schema of the project to your new project

2. Automation, for this you can change the scope of the automation to as many projects as you want and the rule will be applicable for that projects too. As shown in the screen shot.

I hope this will be helpful for you, please don't hesitate if you have any query. Thanks

[Trudy Claspill]

Looks like we both made the same suggestion but you were a little faster! :-)

[Luka Hummel - codefortynine · Accepted solution]

Hi @Marcelo Canaparro

It's great that you've set up a company-based project with custom automations and configurations. To reuse this setup for other projects, you can use the 'Share settings with an existing project' option during project creation. This will copy all the scheme settings.

For automation rules, you can change the scope to include multiple projects, making the rules applicable across these projects. For more advanced templating, you can try our app Deep Clone for Jira, which can help replicate complex project setups including their issues efficiently.

[Bhanu · Accepted solution]

Hi @Marcelo Canaparro 

For copying the Company Managed project configuration, you can use the shared configuration setting instead provided by Jira at the time of project creation.

For Automation, you have to update the scope of the project manually by setting it to run based of the Project Type / Team / manual selection of multiple projects. There is no Rest API for Automation rules to automate this based off of the Project create event. Hope we get them soon.

[Trudy Claspill · Accepted solution]

Hello @Marcelo Canaparro 

When a new project is being created when you get to the final screen where you would enter the project name, then you can choose the Share Settings option.

After selecting that, you can select the existing project that has the configuration you want to use for the new project. Note that this means the new project will use the same schemes as the original project. If you make changes in those schemes it will affect both projects.

This does not copy the agile board associated with the project, nor does it copy Automation Rules, nor does it copy other project-specific information like Components, Versions, or individual issues.

If you want existing rules used by the new projects you could change the scope of the rules to be Global, or to be Multiple Project and add the new project to the rule scope.