Jira Deployment Tab Showing Incorrect Issue Associations

[Namratha Shettigar]

Hello,

We are currently experiencing an issue with the "Deployments" section in our Jira Cloud project.

For example, in the issue EG-414, deployment statuses (e.g., testing, production) are being displayed even though this issue has not been merged to any target branch like qa or master. This is happening across multiple issues where:

• A backend pull request or pipeline merge from another unrelated issue results in deployment statuses appearing on unrelated Jira issues.

• These issues may have been mentioned previously in commit messages or reused branches, but they are not part of the currently deployed code.

We believe that Jira is associating deployments based on older commit references or shared branch history, but this leads to confusion and inaccurate deployment tracking in our project.

---

What I have already tried:

• Verified commit messages and ensured they do not contain the unrelated Jira issue keys.

• Ensured the current issue branch is not merged into staging or production.

• Checked our pipeline setup and branch-environment mapping.

---

Request:

1. Can you guide us on how to prevent this from happening in the future with commit messages or pipeline configuration best practices?

We appreciate any support or insights you can provide.

Best regards,

[Andrii Khorsun]

Hello!

---

We are facing a very similar issue in our Jira Cloud project.
Since July 8, we have noticed that when deploying to production or staging either by merging pull requests or even just manually rebuilding a previously deployed pipeline without new commits, Jira still associates these deployments with unrelated issues.

These issues are often:

• Not part of the deployment commit history,
• Not mentioned in any recent commits or PRs,
• And were not merged into the target branch that is being deployed.

However, Jira still shows the deployment status for them (e.g. “Deployed to production”).

Everything was working as it should until July 8, and we didn't change the deployment process.

This behavior is confusing and leads to incorrect deployment tracking, as old issues are marked as deployed even though nothing related to them was included in the deployment.

We have also checked:

• Commit messages for unrelated issue keys,
• That branches are not reused,
• That only estimated commits are in the release branch.

Any ideas or tips on how to prevent this behavior in the future, whether through commit hygiene, branch strategy, or pipeline configuration, would be greatly appreciated.