Configure and organize recurring projects

[Testy Caracal]

Hi Community,

In my company, we just switched to Jira but wee need advice and best-practices on how to configure and organize our projects.

- Every year we have recurring projects, each with their own same issues, workflow, permissions and kanban board.

- These are datawarehouse/BI projects with SQL or C# scripts to modify year after year.

- We don't use epics or user stories, only tasks, subtasks and bugs.

- We don't need releases or versionning.

For a recurring project :

1) Since we mainly use Kanban boards, what will be the type of project to use ? (Kanban software development ? Business task management ?)

2) How to organise a recurring project ? Do we need to create the same project each year with, for example, a different KEY reflecting its year ? Or do we have to create only one big project and start a one year sprint at the beginning of each year ?

3) Since every issue in a recurring project is the same year by year, how to create a template containing a project and its basic issues ?

4) Will next-gen projects be a solution in our case ?

Thanks in advance for your advices and have a nice day !

[Fabian Lim · Accepted solution]

Hi @Testy Caracal

Here are some recommendations:

1) Use Kanban software it will create the kanban board by default. 

2) you can create one project and then set it up for workflow, permissions, screens. Then if you want to create a new project, you can create it by copying an existing configuration.

However, If it's always the same team of people, you should use 1  project and use components to differentiate  between projects or another single select custom field. 

3) when you create a new project and displays the templates, you will see an option at the bottom to use a shared configuration where you select an existing project

4) not really.

Cheers 

[Testy Caracal]

Hi Fabian,

Thanks for the answer.

- Does the shared configuration option include the copy of issues ? Because this is what we would need.

- As you can see on the picture, we have 3 recurring projects every year. Each of them as a different team of people and its own issues and workflow. So your advice would be to create, every year, 3 projects using the shared configuration option ?

Thx in advance

[Fabian Lim]

I recommend you keep the tasks in a csv with all the necessary fields and import them with the bulk import functionally. This way you don't need to get a plugin.  

Your setup will work well with creating new projects and importing with the csb file.

Cheers

[Testy Caracal]

Hello,

Thanks Fabian, I tested the .csv export/import functionnality + the shared configuration option when creating a project. This works well and is perfect for our needs.

So, in summary :

1) 1 "template" (.csv + shared configuration) for each project

2) Kanban software project type

3) 1 new jira project from template created every year for each recurring project

Have a nice day !

[Marlene Kegel - codefortynine]

Hi @Testy Caracal,

Are you working with Jira cloud or Jira server?

I only ask because you are referring to next-gen (team-managed) Jira projects, but as far as I know they're only available for Jira cloud.

[Testy Caracal]

We are working with Jira server.

[Marlene Kegel - codefortynine]

Our Marketplace app Deep Clone for Jira would meet your use case to

• either clone entire company-managed projects including issues, components, versions and settings
• or Bulk Clone and Move issues to other Jira projects.

Unfortunately it's only available for Jira cloud.

You might find a similar app for Jira server in the Atlassian Marketplace: https://marketplace.atlassian.com/search?hosting=server&product=jira&query=clone

[Testy Caracal]

Unfortunately, for legal reasons we cannot store any data out of our country so Jira Cloud isn't a possible solution for us.