I have a situation where a client has a number of custom fields that need updating to different custom field types. I would prefer to stay out of the database or do project exports, although willing to do it if that is the only option.
Basically the client has successfully been using JIRA for quite some time, but some of the custom fields should be updated to meet newer requirements. For example one field that was only used for numbers before, now should be changed to a text field to bring in additional input.
I can create the second field, but the problem is they have ~400 issues that have values in the current field that will not be in the new field. Since they are not always the same value (where I can bulk edit things over to the new field), I am thinking it would be nice to copy from one field to another.
Another option might be to change the field type (number --> text), although that doesn't seem to be a good option either.
If anyone has any good ideas of some options that would be great.
This method can be used without any add-ons or plugins tested on JIRA OnDemand (Cloud). Also note you can probably use excel format for import but I prefer CSV. I tested this first by creating 3 issues before updating live data, I would suggest you do the same to become comfortable with the process. JIRA Administrator rights are needed for this method.
You may have just made my week by that message!! I had no idea you could import to update issues that easily! Just tested and it works wonders .. thank you SO much!! We did end up managing to get the topic working above .. but your instructions will helps us out with sooooo many other things, thank you again :)
Thanks @Nic Brough [Adaptavist], you gave me an idea.. so
I've found what was wrong!
First of all I've read again Tips for importing CSV data into Jira fields..
Issue Key - You can set the issue key for an imported issue. If an issue with a given key already exists in Jira, it will be updated instead.
The problem was that when you try to do import directly from search result page - there is no mapping field = Jira Key.. and it didn't work with issue id
But when you do it from Jira Admin..->System - there is Jira Key field.
So the solution works as expected.
Try the copy custom field values script from the script runner plugin. This will handle a bunch of conversions, and doesn't need any downtime. So you would create a new field, copy the values, delete the old field, and optionally rename the new field.
Some conversions you can do by changing the database customfieldtype table, but number to text is not one of those, because the storage is different.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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!
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