nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Drawbacks of having large amount of projects on Jira

Rahul Aich [Nagra]

Hi All

Is there any significant drawback of having a large amount of projects (say hundreds and hundreds) as opposed to tens of them on Jira?

The only disadvantage I can think of is that during project import (if required) it would take a lot of time in replicating the configurations on the destination server. But apart from that can you think of any other?

Rahul

Accepted answers

Renjith Pillai

Mostly create Issue page is going to have a severe performance issues with large number of projects (to load all the projects + their issue types).

All comments

JohnA_xb3t2l

Hi Rahul,

Permissions checks are very expensive, so my suspicion would be that permissions management would be your biggest overhead and computational expense from having multiple projects.

All the best,
John

Renjith Pillai

Mostly create Issue page is going to have a severe performance issues with large number of projects (to load all the projects + their issue types).

Rahul Aich [Nagra]

thanks Renjith

Rahul Aich [Nagra]

thanks john for the answer

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira