CustomField Merge after cloud migration

Simon König
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2024

HI,

I wanted to share some difficulties with migration and customfields as well as get some tips and/or tricks.

We are currently migrating and have the problem, that some of our features required redesign in Cloud. Not everything works the same on Cloud as it did on Server (3rd Party stuff mostly)

That's why we decided to setup our Cloud page as we needed to and validate our cloud system beforehand. This also let's us reduce downtime while migrating, because we don't have to configure WF's or something similar afterwards.

 

Not one thing in particular is very time consuming: CustomFields.

When migrating in a similar system, all customfields are newly created with the "migrated" tag. those hold all of our data. Now our setup uses the same customfields, but without the (migrated) tag. because we cannot merge the old and new fields we now have to go ahead and setup everything regarding customfields like Screens, Postfunctions, Filters... to work with the now migrated versions of the fields, then delete the fields we used for the setup, reconfigure everything and then change all customfields with the /migrated) tag so they will look good. As you can see this is just a very high amount of labor and I wanted to ask if someone experienced something similar and how this can be done faster.

Our dataset is big, there a 14k+ Issues, 100+ Customfields for 20+ projekts with 8-10 workflows and 14 Issue Types + postfunctions and automation rules.

 

And help or  experience reports would be appreciated.

 

kind regards

1 answer

2 votes
Valerie Knapp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 13, 2024

Hi @Simon König , thanks for your post. 

For the part about the custom fields with "migrated" appended to the end, I have done a number of migrations for customers and you can contact https://support.atlassian.com/contact/#/ who have a script they can run to remove this for you. 

I think in terms of the pain of analysing an on-premise to go into cloud, you're doing the right thing to rationalise everything. Unfortunately, it is a tedious process that can't really be avoided (in my experience).

Best wishes

 

 

Simon König
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 15, 2024

Hey,

thanks for the reply. It's good to know that this script exists, but, your right, the tedious process remains.

Kind regards

Like Valerie Knapp likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events