Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,463,526
Community Members
 
Community Events
176
Community Groups

Exporting Custom Field Values (indexed + archived)

Edited
Matthew Martin
Matthew Martin Jul 14, 2022

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)

Answer
Watch
Like Scott Nelson likes this
118 views

0 answers

Suggest an answer

Log in or Sign up to answer
Product apps
Adaptavist
TAGS

Atlassian Community Events

See all events