One project with multiple boards or multiple projects

[Alexandra Iuhasz]

Hi,

what would be the recommended way, from the performance point if view, when choosing between:

1. one project with multiple boards (more then 500)

2. multiple projects, each of them having their own board 

In both scenarios we can use, one way or another, versions, epics, filters, components, etc. Therefore the question is only related to the performance. In which if the two options is Jira most probable to scale easier?

Thanks,

Alexandra

[John Funk]

Hi Alexandra - I would group projects by Teams that work together. 10 teams, then 10 projects, etc. 

Are the boards related in anyway as to the teams that work on them?

[Alexandra Iuhasz]

Hi John,

yes they are connected but it's a loose coupling. 

I know that it's a subjective matter, most of it related to the work process, but for all these issues we can find a solution.

My question is therefore related to the performance of the application.

Can Jira deal better with 500 Projects each of them having one board or would it be better to have all tickets in the same project and create 500 boards based on it?

With performance I mean for example loading time for the board.

[John Funk]

I can't speak to the performance issue, but how are you identifying the 500 different boards in the filter for each board? I would think you would need another field besides the Project. 

Personally, I would prefer something in the middle - more like 50 projects or 75 projects if you can group them in anyway.