Jira Instance Cleanup Guide

[rubikcube]

good

[Kristaps Caune]

I do not see the gains for me as a customer. All I see is gains for Atlassian platform by reducing its load and doing the work for you instead of getting useful tips. Endless manual steps, objects for company-managed projects everywhere, ad-tedium jumping between menus. Implement filtering for admin menus and saving of per-uswr settings across the board. I should not have to suffer performance hit dependant on total item count in any admin menu.

Best responsiveness gain I got was when I deleted 200 screens. 

[Graham Zabel]

What about cleaning up boards? We have hundreds of boards and it is very difficult to know which ones are used, and which ones belong to archived/deleted projects.

[Lorenzo Phillips]

@Kim Mooney (and other interested parties) our Instance Auditor for Jira app provides a comprehensive view of items and where/how they're being used. We also provide duplication identification for the following:

• Issue Types & Issue Type Schemes
  • While Jira doesn't allow duplicate issue types, team-managed projects contain isolated issue types which add to the clutter. Our app includes all issue types so admins can see where the types are being used to help identify old team-managed projects that can be archived or removed.
• Workflows & Workflow Schemes
• Fields
  • ALL fields, not just custom fields and we identify duplication from migrating/consolidating systems. You know those pesky fields with (migrated) labels appended to them.
• Screen Schemes
• Priority Schemes

Of course we have a whole host of other capabilities such as customizing your exported data and so on. I'd love to know your thoughts (as well as others on this thread) on our app and if we have any gaps.

We also have Instance Auditor for Confluence that provides a centralized view of information for admins.

Here's a link to our apps: https://marketplace.atlassian.com/search?query=instance%20auditor

Regards,

-Lorenzo