You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all,
Right now, we are walking through a process to reduce the number of custom fields in our environment. A key part of that process is backing up a custom field's data before its deletion, which we will then store indefinitely.
I know that through JQL, we can quickly produce a view of tickets with data associated with a specific field and export. My issue is that, as far as I am aware, ticket searches are based on the index and do not cover archived ticket data. Consequently, I will not get a full view from a JQL search of my potential scope of data. Unarchiving the data to push it into the index at our scale isn't a feasible option.
Maybe I should be going to the database directly, but I would currently prefer a solution that was run out of JIRA in a structured and safe manner as I'm staring down the barrel of needing to remove approximately 400-600 fields.
In so far as the export output, a CSV would be delightful. Any suggestions?
JIRA DC 8.20.8
Scriptrunner (latest)