Since I am not sure how many values you have, lets use this as an example. Next, depending on how many choices are in your drop down field I would suggest using the bulk update to update the field. I would recommend giving this field name something unique from the existing drop down field name. Others may have some suggestions but this is what I would recommend.įirst, create a new field which is text. The value to the new custom field (changing the custom field)Ĭhanging a field from drop down to text field isn't really possible.The issue key to the issue key (so JIRA knows what issues to change).The Summary to Summary (since it’s empty, it won’t do anything, but it’s required).Edit the data to be added in the Custom Field, if needed (for example, if you're moving from a multi-line to a single-line text field, you may need to remove new lines, if it's from text to numeric, make sure there are only numbers, etc.).Add a ‘Summary’ column with no data in any issue (make sure not to add anything to this column other than name in the header, otherwise the summaries will be replaced for all issues it has a value).Remove the first 3 lines and the last line after the data (so there’s only the header and the data).Export as Excel file with those issues containing only these two columns:.Do a JQL search for all issues that are using the other custom field.Migrating Custom Field content to another field using CSV import: Jadhav provided these excellent steps to solve your issue in this thread. You cannot convert an existing drop down field to a text field, but hope is not lost.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |