How would be the best approach from you side for below change.
Custom Field Customer needs to be a multi-select dropdown rather than free form text. This will allow us to create portlets with "Customer" as one of the fields.
There are a number of aspects to this task:
data cleanup of existing records. For example, some tickets have custom field values as VZ, Vz or Verizon. All of these must be cleaned up.
how the migration will deal with tickets that have multiple customers in the free text field
Not a chance of doing this automatically, you're going to need to do it by building specfic scripts and/or manual work.
Beware though - bulk edit *replaces* fields, so if you have two customers like, say, BP and Shell, you need to have *three* filters and three passes through the bulk edit - one for BP, one for Shell and one for BP and Shell (because if you set BP on issue 1, and then use bulk edit to try to "add" Shell, it will overwrite BP, not add it)
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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