Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,293,373
Community Members
 
Community Events
165
Community Groups

Jira Clean Up - System Stats

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

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

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
Site Admin
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,098 views 34 44
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you