Seamless Data Movement: Support for Global & Cross-Project Entities
Hi Atlassian Community!
It's me again, Adithya Ramesh, the Product Manager for Copy Product Data, improving how you control your product footprint in the cloud.
The ability to tweak your footprint becomes not just a nice thing to have but a necessity, especially in large and complex organizations. In our last post, we discussed what we've gone through, that is,
Our tool's capabilities are constantly advancing to meet customer needs. Here's a quick recap of what's new: in the past year, Copy Product Data has expanded to support:
Confluence space migrations between cloud sites, introduced in Q1 2024.
Both Jira Software (JSW) company-managed and team-managed projects are now Generally Available (GA), with releases in Q3 2023 and Q4 2024, respectively.
Jira Service Management form, team-managed, and company-managed projects between cloud sites were released in Q2 of 2024.
A streamlined user experience that gives a consistent plan creation experience, regardless of the specific product for which you create a data copy plan.
But today, I’m excited to discuss what’s next. Based on customer and solution partner feedback, we’ve begun addressing major pain points around copying global and cross-project entities.
What is a cross-project entity?
A cross-project entity refers to an entity with references or dependencies across multiple projects rather than being confined to a single project. Examples include boards, filters, and configurations that span multiple projects, potentially leading to issues during migration if all related projects are migrated separately. Common cross-project entities are Boards, Filters, Advanced Roadmaps, Dashboards, Automation Rules, etc….
What is a global entity?
In the context of Atlassian products, a global entity refers to configurations or elements that are not tied to any specific projects but instead to the site or organization. These entities exist independently of the Object Schemas and can be global or specific to an object schema. Examples of global entities include references, icons, statuses, etc…
You may wonder, “Why are global and cross-project entities important?” Well, support for these entities enables smooth and efficient data movement across different cloud sites, which is crucial for enterprise customers who rely on capabilities like cross-project boards and filters for summary views, leadership reporting, and multi-project team support. Support for these entities will also reduce the manual effort required, allowing us to move towards providing a more seamless experience, something that isn’t always the case, but we want to be soon.
Now I hear you saying, “Yeah, yeah, that’s all well and fine, but what are you delivering?” We’re excited to share that we recently released support for both Cross-Project Boards & Filters and Jira Plans (formerly Advanced Roadmaps)!
But we're not stopping there. Over the next few quarters, you'll witness several additional enhancements aimed at further advancing us towards a truly seamless experience, including support for Global Dashboards.
We're also working towards addressing the issue of Jira entity conflicts when moving data. This problem arises when multiple versions of the same Jira entity, like Custom Fields, Issue Types, or Schemes, persist in the target cloud environment post-migration, resulting in the of duplication of these Jira config entities. As one of our community members aptly put it, "deleting hundreds of groups and then removing 'migrated on' or 'migrated' from all the schemes and fields is very time-consuming."
Our team is actively exploring solutions to manage this duplication effectively, enabling customers to reconcile entities across both migration pathways - Cloud-to-Cloud (C2C) and Data Center to Cloud (DC2C).
But more importantly, back to you
Our team is always looking for feedback on your experience moving data in the cloud. If you have additional feedback about the tool, I’d love to hear that, please feel free to schedule a meeting with me here: https://calendly.com/aramesh-ep0/30min
Was this helpful?
Thanks!
Adithya Ramesh
1 comment