search

solidify / jira-azuredevops-migrator

Tool to migrate work items from Atlassian Jira to Microsoft Azure DevOps/VSTS/TFS.
MIT License
261 stars 223 forks source link

Migrating test details(design steps, test runs, test plans and so on) from Cloud JIRA with X-Ray to Azure #996

Closed KRVijayalakshmi closed 4 months ago

KRVijayalakshmi commented 6 months ago

Read this before submitting your support ticket/bug report

Describe the problem

We need to understand if the jira-azuredevops-migrator will be able to migrate the testing related artifacts example- Test details with design steps, test runs, test plans and linked issues form Cloud Jira with X-ray to ADO. To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Tool version

Attachments

Please attach the following files:

Screenshots If applicable, add screenshots to help explain your problem.

Alexander-Hjelm commented 6 months ago

Hello @KRVijayalakshmi :)

We need to understand if the jira-azuredevops-migrator will be able to migrate the testing related artifacts example- Test details with design steps, test runs, test plans and linked issues form Cloud Jira with X-ray to ADO.

X-Ray test artifacts are supported by our premium offering, in the form of a separate program called the Jira Test Management Migrator which runs on top of the Jira Azure DevOps Migrator.

You can read more here: https://github.com/solidify/jira-azuredevops-migrator?tab=readme-ov-file#jira-test-management-migrator, or visit the product page at our website: https://solidify.dev/products/atlassian-migration-suite

Feel free to reach out to us at support.jira-migrator@solidify.dev

KRVijayalakshmi commented 6 months ago

Thanks for the updates team.

I would like to know more details on premium offering (license details etc.) and any pre-requisites to have the migration successful.

Alexander-Hjelm commented 6 months ago

You can purchase the Atlassian Migration Suite directly from us or via Azure SAAS offerings.

See our website for details + price: https://solidify.dev/products/atlassian-migration-suite.

Here is a pdf (https://github.com/solidify/atlassian-migration-suite-docs/blob/main/migration-jira-test-mgmnt.pdf) which contains among other things:

The tool needs a Windows-based system or VDI to work.

KRVijayalakshmi commented 6 months ago

Thanks for the reference documents.

We have booked the slot for the demo session on 19th Mar 4:20 IST to have more insight before we get into further discussion.

KRVijayalakshmi commented 6 months ago

Post the discussion with the support team in our Demo, we understand that the test runs , pre-conditions, test sets, attachments at the test design step level is still not incorporated in the JIRA Test Management Migrator tool. We may not be able to proceed further as this is the major junk of data that needs to be migrated to Azure. Also, the history will hold the latest change and not all the previous history details which is again a concern area.

However, the support team confirmed to revert with the latest date we may have this feature released which would help us to take it further from that point.

Alexander-Hjelm commented 6 months ago

Post the discussion with the support team in our Demo, we understand that the test runs , pre-conditions, test sets, attachments at the test design step level is still not incorporated in the JIRA Test Management Migrator tool. We may not be able to proceed further as this is the major junk of data that needs to be migrated to Azure. Also, the history will hold the latest change and not all the previous history details which is again a concern area.

However, the support team confirmed to revert with the latest date we may have this feature released which would help us to take it further from that point.

I will check with the Test Management Migrator Team what the status is on Historical test data for the XRay adapter. I will let you know as soon as I know more.

I know that we are in the process of adding this feature for some of the test frameworks, so it could very well be that we could support it shortly.

Payel-roy228 commented 5 months ago

Hi, We need clarification on the below 2 points:

  1. Do we have any in-built importing options for importing the test execution details on ADO side in case we are trying to import the test cases from Excel.
  2. Also do you have any documentation available to access the API details in the test execution level in ADO side.

Thanks in advance!

Alexander-Hjelm commented 5 months ago

@Payel-roy228 The Jira Test Management Migrator is an end-to-end solution and does not integrate with the Excel testdata export. As such, the tool will need live connectivity to both ADO and Jira.

Here is all the documentation which we have available: https://github.com/solidify/atlassian-migration-suite-docs/blob/main/migration-jira-test-mgmnt.pdf

Payel-roy228 commented 5 months ago

@Alexander-Hjelm Hi, we want a clear understanding on the import feature of ADO for test execution/test suite, for ex: do we have an option to import the test execution details which is residing in an Excel sheet. Can you please confirm and elaborate on that. Also, could you please share the API documentation available for ADO to work with test suite level. Thanks!

Alexander-Hjelm commented 5 months ago

@Payel-roy228 In the case of XRay, only test executions inside your Jira instance will be migrated.

You can find the API documentation for Azure Test Plans over at microsoft.com

Payel-roy228 commented 5 months ago

@Alexander-Hjelm Hi, what do you exactly mean when you say, "only test executions inside your JIRA instance will be migrated"? Can you please give an example for that. Are we not supposed to get the test execution status when importing a test case from Excel sheet?
Here, we are not trying to directly migrate the test case from JIRA to ADO, instead we will be importing the test cases along with the test execution details from the Excel sheet to ADO. Hence, we wanted to know if the test execution details will also be imported when we are trying to use the import function in ADO. Thanks!

Alexander-Hjelm commented 5 months ago

I am not sure what you mean by migrating test execution details from an Excel sheet to ADO :)

We only support live migrations directly between your Jira instance and your ADO instance.

As such, you will require a machine with connectivity to both servers/organizations.

Payel-roy228 commented 5 months ago

@Alexander-Hjelm Hi, referring to your below tagged comment that was posted by you after our demo call stating all the limitations. Since we have the mentioned limitations hence, we are trying to refer to the import and export functionalities in ADO on Test suite level. Also, addition to that we don't see the import/export option for the "Execute" tab like we see for "Define" tab. Adding a screenshot for reference.

Also can you please provide us with a template for the exact field level names that can be used to import test cases between JIRA and ADO.

On ADO side, when we are trying to export only the 5-6 columns (like ID, Work Item Type, Title, Test Step, Step Action etc.) are getting extracted though we are adding more columns from the "Column options". Can you please let us know how to export more that these 5-6 fields through export option in excel from ADO.

ADO Test Suite level screens.docx

Post the discussion with the support team in our Demo, we understand that the test runs , pre-conditions, test sets, attachments at the test design step level is still not incorporated in the JIRA Test Management Migrator tool. We may not be able to proceed further as this is the major junk of data that needs to be migrated to Azure. Also, the history will hold the latest change and not all the previous history details which is again a concern area. However, the support team confirmed to revert with the latest date we may have this feature released which would help us to take it further from that point.

I will check with the Test Management Migrator Team what the status is on Historical test data for the XRay adapter. I will let you know as soon as I know more.

I know that we are in the process of adding this feature for some of the test frameworks, so it could very well be that we could support it shortly.

github-actions[bot] commented 4 months ago

This issue is stale because it has been open for 25 days with no activity.

github-actions[bot] commented 4 months ago

This issue was closed because it has been inactive for 5 days since being marked as stale.