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.
I was about to ask if there's a way to do this for multiple projects then saw @Anna Bozhko's comment.
In Jira Cloud, Using the 'import from CSV' option from a search page forces you to specify a single project to import to, however going to the 'external system import' via the admin menu gives you the option to specify the project in the CSV.
WARNING: Depending on which version of JIRA you are running, importing via csv will likely add users to the "Developers" role, per https://jira.atlassian.com/browse/JRASERVER-64769.
I was bitten, so I'm sharing my experience. Also, be very careful of the import itself. As mentioned above, you must have the issue key and summary. For my import, the following fields were required:
I did this with several smaller csv files, in chunks at a time. CHECK to make absolutely sure the "Summary" of the imported data matches the "Summary" of the target issues you intend to update. The import will overwrite the Summary. So long as they match, this isn't a problem.
I have a challenge there Tylor. I have an OOTB column named Description ( wiki style renderer ) , I want to copy that to another field named DescriptionN ( wiki style renderer )
and then hide the original OOTB column .
When i do this on JIRA cloud , using the way you have mentioned above - I lose the rendering.
Not sure How to accomplish this , if you have any solution, please share
Thank you this has saved a huge headache where a user was able to add in a custom field with the exact same name as a Jira default field causing data to be split across different areas and us unable to see which was the right one when using tools such as Advanced Roadmap and Automation Rules!
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.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events