How to managed too many duplicates fields/status in dashboards due to team-managed projects ?

[Perrine HUVETEAU]

Hello to everyone 

We've switched to Jira cloud about 2 years ago and authorized our users (about 3000) to create team-managed projects. 

Everyone is happy with this kind of project but it's very inconvenient when our users want to create dashboards. Where with the company-managed projet, one field/status is unique and shared across projects, with TMP, duplicates are created. Resulting in a very long list of duplicates when configuring widgets. 

In our case, we can have up to 200 "Done" to choose from, and project leads asking us to create pre-fixed custom fields or statuses so they know which one to choose.

We don't want to go there because our Jira instance is already slow (about 700 projects).

Do you have any suggestion or trick to help our users ? 

Thanks for your help

[Nic Brough -Adaptavist-]

I'm afraid the only answers are about process and people, not software solutions. 

You should do one of these:

• stop using team-managed projects (this fielditis problem is a reason we all tell organisations with more than four or five teams that team-managed projects should be turned off - they're not ready for use by large organisations yet)
• tell your teams to stop using custom fields in the team managed projects
• tell your teams to name their custom fields uniquely (simple way to do that is prefix or suffix them with the project key)