Moving customfield values to a different customfield

We just migrated a significant bugzilla environment to JIra (>5000 issues). During the process, either I didn't understand what it was trying to do, or the migration tool not undersntanding what I wanted, but we got a number of new custom fields created and bugzilla data loaded into them. In some cases, the names are the same with the existing fields. An exampe is the Bug_ID; we already had a Bugzilla field, but now we have two :-)

Realistically, this isn't a huge problem, but I see a time in the future when someone will try to create a report including this data and totlally get confused about which field to use.

My question is what is the risk factor if I go into the DB (with Jira down of course) and change the rows of the "bad" customfield to point to the correct customfield (column). This relationship seems to be straight forward and I have actualy done something like this in the past. I just thought I'd ask the expert's opinion. Of course this isn't supported by the vendor and of course I will take prudent backups.

Bill Kepner

1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Jira

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,089 views 0 8
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you