Pull requests from other projects bleeding in

[Dave Poirier]

We have several JIRA projects, and over time many pull requests have the same "number" in different projects.  Say I have project "DLC" and project "TRP", I am in a situtation where I have tickets DLC-1517 and TRP-1517. Each project has its own board, and their own repositories for each platform they support.   

The problem I have, is that one of the TRP-1517 branch and merge request, which happened  months ago, is showing up as a "MERGED" pull request when we are looking at the DLC-1517 story.. which we just opened today.

Is there a setting we missed that is causing TRP-xxxx branch/merges to show up in the DLC project?

[Daniil Penkin]

Hi @Dave Poirier,

As far as I know, Jira tickets are never split into project and number and rather used as is, so such intertwining shouldn't happen just because of the same number in the ticket. Jira development panel that you took the screenshot of looks for references to the ticket in commit messages, branch names and pull request metadata.

I would suggest to open a support case and privately discuss and share more information so that we can find the root cause.

Thank you.

Daniil

[vovan1]

Hello Community,

we face similiar issue.

Our 2nd Team noted that Pull Request for merging master into feature branch of 1st Team(feature/Team1) is being displayed in the 2nd Team's pull requests. Where we need this merge to get latest commits from the other teams. And they get confused seeing that their issues are open again.

Is there still no resolution/workaround for this?