Jira to Azure DevOps (Official) Add-on - showing tickets as deployed multiple times

[Yuliya Spiridonova]

Hello Atlassian Community,

We are running a trial of the Jira to Azure DevOps Official Add-on which works well,

Azure DevOps for Jira (Official) | Atlassian Marketplace

but we noticed the same Jira tickets are showing as deployed over and over again.

____________________________________________________________

Example: Jira ticket JIRA-1 was originally added to the repo on 1st October, it was deployed on 5th October.

Then we added JIRA-2 on October 8th and deployed it on October 10th, then JIRA-3 was added to the repo on October 12th and deployed on October 15th.  

In this case, JIRA-1 shows deployments done on October 5th, October 10th, October 15th etc. Ideally, I would expect it to stop after the original deployment on October 5th.

____________________________________________________________

Did you have the same issue and is there any way for it to show only the original first deployment, unless we re-add the same ticket to the repository again? It means we are not able to run reports on our deployments as the same tickets are shown as deployed over and over again.

[LynnG]

What you're describing actually sounds consistent with how Jira deployment tracking is designed to work, rather than a bug.

According to Atlassian's deployment integration documentation, a Jira issue is associated with a deployment whenever a deployment contains commits that are linked to that issue. Jira shows deployment information based on the commits included in each deployment, not only on the first deployment in which the issue appeared. [support.at...assian.com], [support.at...assian.com]

Using your example:

Deployment Date	Changes Included
Oct 5	JIRA-1
Oct 10	JIRA-1, JIRA-2
Oct 15	JIRA-1, JIRA-2, JIRA-3

If the later deployments are promoting the same commit history (for example, moving the same release forward through environments or deploying from a branch that still contains the JIRA-1 commit), Jira can continue to associate JIRA-1 with those deployments. As a result, JIRA-1 may appear as having been deployed multiple times. [support.at...assian.com]

Unfortunately, from the Atlassian sources I found, there is no documented setting in the Azure DevOps for Jira (Official) app that changes this behavior to "show only the first deployment" for an issue. I found a community post that describes the exact same scenario, but it does not contain an official solution or configuration option. [community....assian.com]

What you can do

• Review whether your Azure DevOps deployment pipeline is repeatedly deploying the same commit set to the same environment.
• Check whether deployments are being reported for multiple environments (Dev, Test, Prod), as Jira intentionally tracks deployments across environments. [support.at...assian.com]
• Raise a support ticket with Atlassian to confirm whether there is a newer configuration option or roadmap item for "first deployment only" reporting, since the public documentation does not mention such a feature. [support.at...assian.com], [community....assian.com]

If you can share a screenshot of the Jira deployment panel for one of the affected tickets (with sensitive information obscured), I can help determine whether the repeated entries are expected environment promotions or potentially an integration configuration issue.