Multiple projects for one team-need one backlog

Question

I am trying to set-up Jira for company. We have about 20 teams. We have grouped these teams into "Areas". Each "area" will be a Project in Jira. However, I have services teams that support multiple areas. They will now need to maintain multiple backlogs.

How can I effectively manage this?

Should i just create one big project with those 20 teams and create Quick filters?I do not want these services teams to maintain multiple backlogs in the different projects.

Or keep Areas as separate Projects and then have the Services teams create Boards for multiple projects?

Jack Brickey · Answer

The number is not a concern. It just comes down to the likelyhood that the teams want to configure their workflows differently. You can always move a teams issues to new projects later as long as you have some field you can filter on to distinguish them from the rest.

Zara_ix0jyf · Answer

@Jack Brickey

If I have 25+  teams under One project- would it be difficult to maintain? Would there be any performance issues?

They all follow the same release cycle.

I guess I am trying to figure out the best way to approach this (and the less painful way).

Jack Brickey · Answer

I can’t say what is best. My opinion would depend on really understanding your environment, team, culture, processes. However, generally I stick with a single project if the issuetypes, workflows, permissions, screen schemes etc. are the same. Otherwise I split the project. Now with that said, if these are truly different “products” with independent release cycles and teams I would have a project for each. To me, at least for SW development Jira’s Projects have a 1:1 relationship with my “products”.