Comments
-
Start by auditing your ServiceNow instance and removing outdated catalog items, workflows, fields, and records. Run a free demo migration with sample data, review the results, adjust your mapping, then migrate the full historical dataset. Before go-live, run a delta migration to capture recent changes, keep both systems…
-
@Matthew Sinclair Yes, still a real issue — especially Cloud-to-Cloud and DC-to-Cloud. It usually comes down to matching logic: if field name, type, description, or context don't line up exactly on both sides, the target creates a new field instead of mapping to the existing one — repeated/staggered migrations from the…
-
@Alan Bruce Thanks for adding this — and congrats on getting through a Data Center to Cloud move! Great callout on Jira Assets — that's a common gap I didn't cover, and worth its own deep dive. Asset custom fields and object relationships often need separate handling rather than assuming they'll ride along with the project…
-
For a 3-to-1 JSM consolidation, I’d recommend planning the migration around the target instance and permissions model first. You can consolidate projects, tickets, users, attachments, and configurations from multiple Jira/JSM instances, then set up project roles, permission schemes, and issue security so each team only…
-
There's no way to map top_agent_id to an agent name yet — Atlassian hasn't documented one, and there's no public API for it either. Workarounds: Compare your CSV's daily trigger counts against the Agents tab in Rovo Insights (UI shows names + usage) to infer which ID is which agent. Check each agent's profile URL in…
-
These are great improvements, especially the native automation for status updates. For companies migrating from platforms such as Zendesk to Jira Service Management, incident communication is often important, as well as migrating tickets and knowledge base content. One question: are there plans to support migration or bulk…
-
I've seen similar questions during Jira Data Center → Cloud migrations. Unfortunately, multilingual content often requires review after migration because Cloud handles translations and localized content differently than Data Center. There isn't a built-in way to automatically accept all language reviews across projects. If…
-
Workforce Management is another example of why a Jira Service Management migration should be more than just moving tickets and users. Native routing and workforce optimization rely on clean data, well-structured teams, and accurate assignment rules. Taking the time to optimize these during migration will help to get the…
-
A few things can affect Rovo's responses, including the amount of context available in the ticket, permissions to related issues or knowledge sources, and how the prompt is structured. Is Rovo producing a generic RCA, an incorrect one, or no output at all? Also, is this happening with a single ticket or across multiple…
-
Great to see the new admin experience rolling out. From a migration perspective, UI and terminology changes are also a good reminder to review internal documentation, runbooks, and admin training after any platform update. While configurations remain intact, keeping teams aligned on the new navigation and terminology helps…
