Jira Deployment Tab Showing Incorrect Issue Associations

[Namratha Shettigar]

Hello Atlassian Support,

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 we’ve 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 help us remove the incorrect deployment entries from the affected Jira issues (e.g., INDY-414)?

2. Is there a way to manually disassociate deployments from a Jira issue card?

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

We appreciate any support or insights you can provide.

Best regards,

[Heenaben Sardarbhai Chaudhary]

Hi there,

You're experiencing deployment statuses appearing in unrelated Jira issues because Jira links deployments based on any mention of the issue key in commits, branches, or PRs—even if those aren’t currently part of the deployed code.

Why this happens

Jira's deployment tab shows all deployment events associated with commit SHAs that reference the issue key anywhere in the code history community.atlassian.com+10community.atlassian.com+10support.atlassian.com+10.

Best practices to avoid future mismatches

1. Use precise commit messages
   Avoid including unrelated issue keys in commit messages. Keep it to just the key(s) directly related to that change.
2. Clean branch naming strategy

• Use structured branch names like feature/EG-XXX-description.
• Don’t reuse branches across issues; delete or close them after merging.

3. Map pipeline to environments explicitly
   Ensure your CI/CD pipelines only reference branches meant for specific environments (e.g., release/* or qa/*). Avoid running deployments on long-running feature branches.
4. Use .jira/config.yml for custom environments
   If you use non-standard environment names, define them to ensure clarity in Jira deployment mapping .
5. Consider cleaning up associations
   If previous commits erroneously link an issue to a deployment, you can:

• Edit commit-to-issue mapping manually (via GitKraken or Git Integration apps) help.gitkraken.com, or
• Use the Deployments REST API to gradually remove unwanted associations.

In summary:

• Only include issue keys in commits/branches when directly relevant.
• Follow clean branch-per-issue practices.
• Configure CI/CD to deploy only intended branches.
• Map custom environments clearly with .jira/config.yml.

These steps will ensure your Jira deployment tab remains accurate and relevant.

regards,
Heena.