You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Hi all,
Having read some posts online, once a data type for a custom field has been added, it's pretty much set in stone. The easiest option appears to be create a new custom field and migrate the ticket information across. But what is the best way of going about this?
It was my mistake to begin with. An internal reference (which is just six numbers) I created as a text field. Now, with nearly some 500 tasks generated later, I'm wondering if I can create a new numeric reference field and migrate the tickets to use this field instead?
Is this possible?
Kind regards,
Darren.
One way of doing it is to use an automation rule, I would use a scheduled one because you manually trigger that one, that copies the value from your text field over to the new numeric field.
After you create the new field you could export all your data, then bulk import the data back into Jira with value going to the new field. Then you would remove the old text field from the screen.
Or you could use an automation rule to loop through all your issues and copy from one field to the other.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.