From 96cb1a395dbcf98e7106dad9fd6e9d970080deb3 Mon Sep 17 00:00:00 2001 From: Alexander Hjelm Date: Thu, 7 Nov 2024 11:30:18 +0100 Subject: [PATCH] Update readme.md --- readme.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/readme.md b/readme.md index 27e4cebe..554ee2ff 100644 --- a/readme.md +++ b/readme.md @@ -82,7 +82,7 @@ Contact us at [support.jira-migrator@solidify.dev](mailto:support.jira-migrator@ **Jira Azure DevOps Migrator PRO** contains all the features in the Community Edition, plus the following additional functionality: -- Migrate **Releases** and the **fixes version** field +- Migrate **Releases** and the **Fixes Version** and **Affects Version** fields - Release date, start date, release status and release description - Migrate **Branch links** from Bitbucket to Azure DevOps. - Migrate **Sprint Dates**. @@ -91,7 +91,7 @@ Contact us at [support.jira-migrator@solidify.dev](mailto:support.jira-migrator@ - 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. - Support for state transition dates (e.g. `ActivatedDate`, `ClosedDate`) for workflows with custom states. By default, only **New**, **Closed** and **Done** are supported. - Select any property for **object**- and **array**-type fields for mapping. This allows for: - - More possibilities when mapping the **fixes version** and **components** fields. + - More possibilities when mapping the **Fixes Version**, **Affects Version** fields and **Components** fields. - More possibilities when **mapping Azure DevOps **custom** ### Jira Azure DevOps Migrator Bootstrapper