Hi Community,
As many of us are navigating the journey from Data Center to Cloud, one of the most technical challenges often involves migrating complex ScriptRunner logic or local Groovy scripts.
While working on several migration projects recently, I observed that while the data moves over, the logic often needs significant refactoring. I wanted to share 3 specific technical patterns that often break silently, in hopes it helps others during their transition.
1. Hardcoded IDs vs. Name Lookup
In DC environments, it was common practice to reference Custom Field IDs directly (e.g., customfield_10200).
The Challenge: On Cloud, these IDs are re-generated.
Best Practice: Refactor scripts to look up fields by Name dynamically, or verify the new IDs immediately after sandbox cloning.
2. User Object Changes (GDPR)
This is the most frequent error I encounter. The user.name property (often used for string-based assignment) is deprecated or behaves differently due to GDPR privacy standards.
The Fix: Ensure your scripts interact with the accountId rather than username strings.
3. Trigger Gaps
Some event listeners available on Server (e.g., specific UI interactions) do not have direct equivalents in Cloud Automation. In these cases, using Incoming Webhooks can often serve as a reliable bridge.
Let's discuss:
For those who have completed their migration, what was the one script or rule that gave you the most trouble? Feel free to share your experiences (or error logs!) below.
Thanks,
Ethan
