What is the best template to use for a single team with multiple projects?

Nigel Hardwick

I work in a small, self organising team and I want to know the best way to set Jira up for a single team with multiple projects and ad-hoc tasks. Do I use the team managed project template, create a single project for the team and then represent projects as issues and the underlying tasks as sub issues or should I create multiple projects and use a board to manage them.?

Trudy P Claspill

Hello @Nigel Hardwick 

Welcome to the community.

Do the projects have distinct release cycles?

Are you planning to work in a Scrum method, or a Kanban method, or will the team use both methods?

Are you planning to stay on the Free subscription or are you planning to move to a paid subscription?

How much control do you need to maintain over things like custom fields and workflows?

Should all members of the team have the same level of access to work with the issues in all "projects"?

Will all tasks across all "projects" follow the same workflow, and need to have the same custom fields?

What are your reporting needs for aggregating the data across all the "projects" into a single report?

One thing to be aware of if you choose to use Team Managed projects is that those do not directly support using multiple boards, or using one board to show all issues across multiple Team Managed projects. You can manually create a board from a Save Filter that pulls information from multiple Team Managed projects, but the board created in that manner does not function quite the same as the default board associated with a Team Managed project.