Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

Best practice to store deprecated custom field data before removing

Hi Team,

As part of housekeeping, we are planning to remove deprecated/not used custom fields from the jira and planning to store same field data before performing housekeeping activity for future reference, So please suggest best practice to do this activity and store the data in easy way to restore if required in future.

We are using Jira v8.22.6.

1 answer

0 votes
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 28, 2023

Hi @Sreenivas Narala 

I think the easiest way to accomplish this is to execute a search like this:


In your results, include at least the project, issue key, Summary, and custom field and then export the results to csv

Should you ever need to restore, you could use the csv export as an import file for restore.

Suggest an answer

Log in or Sign up to answer