Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-678

Allow for multiple versions in cloudMigrationAssistantCompatibility

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently only one value is allowed in cloudMigrationAssistantCompatibility and this is the minimum version of an app.

      This can cause issues with CMAs where there are multiple versions of an app for different versions of Jira or Confluence. For example, a Partner might have an app with versions

      • 4.5.0 for Jira 7 versions only
      • 6.2.0 for Jira 8 versions only

      But for cloudMigrationAssistantCompatibility, if they enter 4.5.0 as the minimum version then anything after 4.5.0 (e.g. 5.x, 6.0 before the 6.2.0 version) will be set as compatible.

      Workaround

      As semantic versioning is used to compare versions, and Marketplace has the ability to limit versions with a maximum and minimum value, the Partner can use versions like

      • 7.0.0-jira7 for Jira 7 versions only
      • 7.0.0-jira8 for Jira 8 versions only

      as the build information section of the version at the end is not used for comparison.

              jjardim2@atlassian.com Jurandir Jardim (Inactive)
              jrichards@atlassian.com James Richards
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: