Guidance on single vs multiple project creation

Question

Hello Team,

I am looking for some guidance on below

I am working for an ERP program as everything was set under one project, currently the kanban board got areound 9000 issues for build phase, and the team will start build and testing phase soon in couple of weeks. i have recommended them to create a new project as the current board already got 9000 issues. team asked whether new kanban board creation will solve the problem.

I need experts recommendations here whether to go with an existing project different boards or project compeltely , if i have to recommended project becuase of JIRA technical issues what will those technical issues.

Please note, there is lot of reporting that exists in the currently project, and similar reporting may be required on new issues that will be created.

Arkadiusz Wroblewski · Answer

Hello @keerthi_guntupalli

A new Kanban board only helps if the board filter is tighter. A board is basically just JQL + columns, if the new board still includes those ~9000 issues, you’ll just recreate the same problem in a new place.

What can bite you technically with one huge board:

Performance: boards get slow when they have to load/render thousands of issues.

Visibility limits: depending on setup, you can run into “not everything shows” behavior and people miss items.

Day-to-day pain: ranking, searching, moving issues becomes more annoying simply due to volume.

Best practice (especially since you already have reporting in the project):

Keep the same project (so dashboards/reports/workflows don’t get duplicated)

Create separate boards per phase/workstream with strict filters, e.g.:

Build/Test board: only unresolved + only Build/Test statuses (and maybe last X months)

Intake board: only new/triage statuses

When I’d recommend a new project:

only if you truly need different permissions, workflow model, or separate reporting boundaries.

So my advice to the team: don’t split projects just because the board is big. Split the boards by phase with better filters. You’ll get the benefit without breaking your reporting.

Please understand that every Site differ so, to give more best practice advices, we need more details.

Have a great day ☀️🤠

Trudy P Claspill · Answer

Hello @keerthi_guntupalli

What problems are you encountering at this point?

Are the issues somehow divided among teams that will address them? If so, what have you done to apply that team identification?

What kind of project does this concern? Click on the ... button next to the Project/Space name in the navigation panel on the left. Tell us what the last two lines in the pop-up say. That will be something like:

Software space
Company-managed

Are you planning to use Scrum or Kanban methodology to get through the work?

What kind of reports do you already have set up? Are the reports pulling data for the entire project, or are those reports based on pulling subsets of data based on some field values in the issues.

If you have used some field in the issues to divide the work among teams then you could create separate boards for each team, by creating a saved Filter to get the issues for each team and then creating a board based on each saved Filter.