How to migrate custom field values with groovy or not?

 Hi!

Today I would like to share a possible way to migrate or merge a custom field during a periodical cleanup. 

Possible ways are built-in functionality of Scriptrunner or myGroovy, own code and own yet another alternative way for the complicated situation.

Also,you can follow with next typical steps of cleanup process:

  1. Detect the fields
  2. Create a ticket about merge plan 
  3. Detect the JQL, agile boards queries via database queries in tables searchrequest, add info into ticket
  4. Prepare the optimized the context in the comment of ticket
  5. Notify project stakeholders in the Jira ticket
  6. Get approvals 
  7. Inform via slack (email) the next merge the end users affected  for  that changes
  8. Execute the action.

This is my typical process for the cleanup activity.

As an example, let’s do the next real case with screenshots.

 

Goal:

Migrate from the Production environment field to Products field. Both fields are pickers. 

image.png

Where some of options are the same, if you see the small differences, you can change if both need to be merged.

image.png

Then under super user which has access to all related projects, create filters with related tickets.

image.png

Then I saved the filter with name test_ . 

After visiting the Scriptrunner built-in scripts to copy custom fields values.

image.png

After verify via preview and run.

image.png

Hooray we merged. 

After using the new feature (https://jira.atlassian.com/browse/JRASERVER-41269) from 8.11.0, we can adjust the private filters via gui, if it’s needed. And public stuff as well via gui.


Comments

  1. This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

How only 2 parameters of PostgreSQL reduced anomaly of Jira Data Center nodes

Atlassian Community, let's collaborate and provide stats to vendors about our SQL index usage

Stories about detecting Atlassian Confluence bottlenecks with APM tool [part 1]