Development panel pulling commits/PRs from other stories

[Matt Parks]

In the Development panel, the expectation is that, if the Summary of the commit message in Bitbucket contains a Jira issue key, that commit, and any artifacts associated to that commit (e.g. PRs, branches) will display on the associated Jira issue.

However, it appears that, instead of looking only for that specific issue key, if the key is very similar, it will pull in as well.

For example, we have two separate projects with keys of DEVOPS and DEVOPSSUPP (one is for our DevOps team to track their work, the other is to intake support requests from the IT floor).

They reported that, on the Development panel for DEVOPSSUPP-929, it was pulling in the commits and PRs for DEVOPS-929. When I go to that issue and drill into the commits, I can see that they are, in fact, associated with DEVOPS-929, even though I'm on the DEVOPSSUPP-929 issue.

My questions are whether this is expected behavior and whether it is possible to configure that it does an exact match instead of a "like" search. My guess is it is not possible to configure how this works and therefore this is always a possibility when the project keys are similar, but I wanted to see if anyone in the Community has any knowledge.

[Mohanraj Thangamuthu]

Hello, Good day. By any chance, project key got changed between DEVOPSSUPP & DEVOPS ?. This way old key is still pointing to different project.

[Matt Parks]

No, they are two independent projects. For example, DEVOPS-929 and DEVOPSSUPP-929 are both currently active issues.

I see the Commits and PRs on both issues. But they should only be visible on DEVOPS-929, since that is the issue key that was used in the summary of the commit messages.