Does anyone have some ideas how to change custom field ype?
Unfortunately, we just fall into "Please note that this workaround is only applicable when you have many issues containing the same custom field value. As a scenario let's say you have 100 issues, and each issue have different value for the custom field, it will be very difficult for you to perform the migration by using the steps below."
We have almost 1000 issues in JIRA now. Those issues have different values for the custom field: Weight. We want to change it from Text Field to Number Field and keep value no missing/overriden. Any solution for this kind of situation?
Upgrading custom fields is for Single Version, Multi Version, Single Select, Multi Select, Multi User. I didn't see any more details address my situation.
Does anyone help? Thank you very much.
Thank you for your quick reply, rambanam prasad and Nic Brough
@Nic Brough, could you explain with more details to use bulk edit method: copy old text field value to new number field? I do need to keep those values(they are number like 996, 98 but in text field for the moment). When use bulk edit I just see the option to input new value, this will overwrite my different values with the same value. Thank you very much for your help.
Sorry, I wasn't clear there. Bulk edit can only set one value at a time, but on a range of issues. So you'd have to analyse your number values and potentially make hundreds or thousands of edits.
That's also why I mentioned the script runner. If my analysis says I've only got a tiny handful of values (like they're all going to end up as 1, 2, 4, 8 or 16 in the new field), I'd bulk edit. If it turns out I've got 1000 different numbers on 1000 different issues, then I'd be reaching for scripting of some sort.
The document you have found also has the problem that you can't change between field types that store their data differently. Text fields store text, and number fields store numbers, so you really do not have an easy migration here. "Changing type" is basically inappropriate and you have a migration to do.
What I would do:
Note that if you stick with "change field type", the process is
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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