Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-95292

To Support associating more than 200 issues with a single deployment in Azure DevOps integrations

XMLWordPrintable

    • 1

    • 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.

      Issue Summary

      Currently, when integrating Azure DevOps with Jira, there is a limitation where only the most recent 200 work items (issues) can be associated with a deployment due to Azure DevOps REST API’s default pagination limit. This means that for deployments referencing more than 200 commits, any issues beyond the 200th commit are not tracked or displayed in Jira’s deployment records. This limitation impacts customers with large-scale deployments who require comprehensive traceability of all issues included in a release.

      Steps to Reproduce

      1. Perform Deployment on Azure Devops above 200 commits through more than 200 issues.
      2. Go to the Jira Work item, select the development section and view the deployments.

      Expected Results

      • Display all deployments on the Development Tab on the work item 

      Actual Results

      • Does not display all deployments on the Development Tab on the work item which are above 200 work items associated with them recently.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Unassigned Unassigned
              6ddbd1c1e1be Dishon Victor
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: