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; } } }

Running JIRA with lots of projects

Jo-Anne MacLeod

Has anyone tried to run an instance of JIRA with more than 900 projects? There will be a lot of issues as well, but not at the magic 200k number yet. Before you ask it is not possible at this time to combine the files, there are some differences between each one.

I know that memory may be an issue, but is there anything else that we should be thinking about as well?

Accepted answers

JamieA

I've worked with several around that figure. The worst thing about it is some of the admin screens, eg viewing the workflow schemes page, and other schemes page. The project dropdown in the planning board is horrible too... other than that last one I don't think the effects on the user visible parts of it are particularly noticeable.

What's worse is that number of custom fields.

All comments

JamieA

What's worse is that number of custom fields.

Jo-Anne MacLeod

Thanks Jamie, I was kind of hoping that you would say something like that. I can't imagine dealing with 900 custom fields...yuck!

Jim Birch

Seconded. Use very miserly rules and standards for custom fields and screens to stop maintenance/management from going out of control. We stick to a limited number of project "schemes" and require our projects (like 150) to square hole into the standard schemes.

The scheme page display problems should be handled with expanders like project user lists. Is there an enhancement request on this?

Jim Birch

Created enhancement request for rolled up lists with expanders. Add your vote

https://jira.atlassian.com/browse/JRA-25690

Welcome!

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

Quick Links

Find more posts tagged with

jira