Is there any performance benefit to be gained in how we model projects?

unknown

We currently have over 200 projects in our system and 400,000 issues.  I am looking to clean up the configuration we use to a single standard configuration that all teams will use.

Would it be more sensible to have a single project that holds all issues or multiple projects with the issues shared between them?

Jorden Van Bogaert

Hi @[deleted]

I don't think putting everything in one project is going to give you performance improvement, I think it may even cause the opposite.

Things to think about is shared scheme configuration, trying to use simple workflows (the more steps a workflow has, the complexer it gets, which over time may impact performance), but one that we found especially useful is setting custom fields contexts.

Find out which projects and issue types use which custom fields and restrict the custom field context to those specifics. If the context is set to 'global', the field will be available on every issue, even though it's not on the screen. This causes a bigger index, which impacts searching and indexing performance.

What can also help is deleting older projects (or keeping an offline backup of them somewhere), but only do this when you don't expect to ever need the data again. Also delete projects that may have been setup simply as a test or projects that remain empty.

These are all small things that may help

Hope it's useful.

Kind regards
Jorden