Jira Clean Up - System Stats

Rebecca Hylek
Contributor
May 30, 2022

We recently migrated our on-prem Jira Data Center to the Cloud and would like to begin a project to clean up our environment.  I'm looking for a way to export a list and/or total number of the following items:

  • Version
  • Components
  • Custom Fields
  • Issue Security Levels
  • Issue Types
  • Screen Schemes
  • Screens
  • Statuses
  • Workflows

Is there an easy way to do this in Jira Cloud?

Thank you!

Becky Hylek

2 answers

0 votes
Mayur Jadhav
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2022

Hi @Rebecca Hylek 

Welcome to the Atlassian Community!!!

There is no way to export the custom fields, statuses, etc out of the box.

They are two ways to do it either by Manually- Ideally too much time consuming or the second way to do it by using third party add-on which is available in the Atlassian Marketplace and the add-on name is Optimiser for Jira .

 

 

Cheers,
Mayur

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 30, 2022

Sadly, no.  There is in Server and DC for some of the items on your list, but not in Cloud.  I'm afraid you'll need to plough through them manually.

You'll also find that a flat list of this stuff is not actually useful in defining what you want to clean up.   A simple list of versions is of no use in housekeeping, you probably want to know what versions are in use and in which project and by volume.  Similarly for all the schemes - a flat list is not going to tell you much, you'll want to be looking at how it is used.  And the best place to do that is inside the application!

There are several ways you could try to analyse usage, and your choice of which way to go should be determined by your people's pattern of usage.  Would it be best to look at it project by project?  Team by team?  Or more useful to approach it from the point of view of the reporting you are doing - what fields are actually useful?

Either way, before you even start any usage questions, do some basic housekeeping - go into each config list (permission schemes, notification schemes, workflows, workflow schemes, screens etc.  But not fields, those do not have functions that make this easy).  No need to analyse anything, just delete anything that is "inactive" - not used by any project.

This will make your usage analysis a lot quicker and easier because you won't have to be looking at things that are not in any use.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events