Early Access Program for solving duplication of Jira entities when using Copy Product Data

[#1]

Hello Everyone!

I am Adithya, Product Manager for Copy Product Data - the tool used to perform data copies between cloud sites. We heard your feedback that the issue with duplication of Jira entities is a big hurdle to effectively copying data. I am thrilled to share that we are working on a comprehensive solution to this problem to allow you to make decisions on how conflicting entities should be handled before performing the data copy. We expect this to significantly help in reducing the effort taken for post-migration clean-up. Before we make this feature generally available, we’re looking for individuals who would like to partner with us to ensure our solution meets your needs in an Early Access Program.

Who are we looking for?

Jira cloud admins who:

• have org admin permissions

• Manage data across multiple cloud sites

• You’re on Cloud Premium or Cloud Enterprise Plan

• Manage 500+ users

What will the solution solve?

Please note that our initial solution will be able to identify, prior to the migration, which of the following entities will be duplicated based on entity name and type, that are:

• CustomField

• CustomFieldScheme

• FieldLayout

• FieldLayoutScheme

• Project role
  

• IssueType

• Permission scheme

and provide you with the following options:

• Map source entity to an existing destination entity where destination overrides the source

• Rename source entity on destination

• Do not map source to any destination entity (existing behaviour)

How to sign up for the EAP?

Step 1: Sign up here: https://earlyaccessprogram.atlassian.net/servicedesk/customer/portal/363

Step 2: We’ll reach out by the end of November to confirm your participation.

Step 3: We will then enable the solution on your site(s) when you use the Copy Product Data tool.

What’s in it for you?

• An opportunity to provide direct feedback to our product team, which will go into shaping this new copy data feature for everyone

• Engagement time with our product team

• Behind the scenes look at how we’ve built this feature and how it works

How long will this EAP run?

This EAP program will run for a maximum of 3 months from the start date for the team to evaluate the solution we have built. Atlassian reserves the right to end this EAP earlier if we receive satisfactory levels of customer feedback sooner. Based on the results, the feature will then be available as a beta later.

Questions?

This EAP is one of the many exciting things we’re building to empower your teams to do more with your data in the cloud. If you have any questions about this program, terms and conditions, or your eligibility for early access, feel free to comment below.

Edit: We are now closing new applications to the EAP as we have reached the requisite levels of participation. 

[Cengiz Akyildiz]

Sounds just the right time! Already submitted a request. Thanks for sharing.

[Hubert Kut]

Hi Adithya,

Let’s connect! As part of Atlassian Ventures, we developed Doctor Pro for Jira, a specialized tool designed to address challenges like object duplication, particularly custom fields, following migrations or instance merges in the cloud.

Doctor Pro for Jira features 21 in-depth reports to analyze configurations and identify issues such as duplications. Additionally, it includes a robust merging mechanism for custom fields, which not only transfers data but also updates filters and screens to ensure seamless functionality.

Looking forward to discussing this further!

Best regards,
Hubert

[Andy P]

Interested but getting a "don't have permission" trying to sign up... ?

[Steve Rhodes]

I also do not have permission to access the portal. I have a login at the earlyaccess JSM but not this specific portal.

[Karla Rivera]

How do we subscribe if there are no permissions to access the portal? Or is it already closed by date?