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,