Jira orb labels jira tickets with wrong builds

At 15Five we just integrated in https://circleci.com/orbs/registry/orb/circleci/jira and connected it to our jira cloud instance.

We have had a few cases where jira tickets get linked to the wrong build. For example ENG-2441 got linked to a build for the branch ENG-2602-Backend-Keyword-search . ENG-2602 is a different ticket and I’m not sure why it was linked to ENG-2441.

The title of the commit that started the build is “Merge branch ‘dev’ into ENG-2602-Backend-Keyword-search” so I have no idea why ENG-2441 got referenced.

We had the same problem. Got to the bottom of the issue by looking at
https://circleci.com/api/v1.1/project/github/ORGANISATION/PROJECT/BUILD_NUM, for some reason the all_commit_details node contained a commit that GITHUB wasn’t showing in the Pull Request.

Unfortunately don’t have a workaround, we have forked the orb and will perform our own integrity checks.

seems like the integration should be revised (plugin configuration etc…)