-
-
Notifications
You must be signed in to change notification settings - Fork 239
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update ADO marketplace readme. Fix spelling in README.md
- Loading branch information
1 parent
4ac81b8
commit 7ebb541
Showing
2 changed files
with
31 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -28,12 +28,38 @@ The tools are provided as-is and will require detailed understanding of how to m | |
* Read the article [Jira to VSTS migration: migrating work items](https://solidify.se/blog/jira-to-vsts-migration-work-items) for more context of the process. | ||
* Read the article [Jira to Azure DevOps (VSTS or TFS) migration](https://solidify.se/blog/jira-azure-devops-migration) for a complete step-by-step walkthrough on a migration. | ||
|
||
# Tested with | ||
## Jira Azure DevOps Migrator PRO | ||
|
||
The Jira to Azure DevOps work item migration tool has been tested on the following configurations: | ||
The **Jira Azure DevOps Migrator PRO offering** from Solidify offers more features and utilities to further increase your migration capabilities and streamline the migration workflow. [Contact us for more information](mailto:[email protected]) | ||
|
||
### Features | ||
|
||
**Jira Azure DevOps Migrator PRO** contains all the features in the **Community Edition**, plus the following additional functionality: | ||
|
||
- Priority support | ||
- Composite field mapper (consolidate multiple Jira fields into a single ADO field) | ||
- Migrate **Releases** and the **fixes version** field | ||
- Migrate **Remote Links** (Web links) to Work Item hyperlinks. | ||
- Correct any **Embedded Links to Jira Issues** in text fields such as Description, Repro Steps and comments, so that they point to the correct Work Item in Azure DevOps. | ||
- Select any property for **object**- and **array**-type fields for mapping. This allows for: | ||
- More possibilities when mapping the **fixes version** and **components** fields. | ||
- Support for mapping **custom user picker** fields. | ||
- Utilities for automating user mapping between Jira and Azure DevOps | ||
- Utilities for automatically generating the Jira Azure DevOps Migrator configuration file, thus enabling you to get started migrating faster | ||
- Utilities for viewing the Jira workflow and assisting with field and state mapping | ||
|
||
## Supported versions of ADO/Jira | ||
|
||
The Jira to Azure DevOps work item migration tool is officially supported on the following platforms: | ||
|
||
- Atlassian Jira Cloud | ||
- Atlassian Jira Server 7.0.0 | ||
- Atlassian Jira Server | ||
- 7.x | ||
- 8.x | ||
- 9.x | ||
- Azure DevOps Services | ||
- Azure DevOps Server ("TFS 2019") | ||
- Azure DevOps Server | ||
- 2022 | ||
- 2020 | ||
- 2019 | ||
- Team Foundation Server 2018 update 3 |