Tickets are not picked-up by deployment

[Vlad Kusok]

Hey All,

Looks like we are running into an issue sometimes, we are using the Git-Flow approach during development, however after we create the release/* branch from develop and deploy from the release/* branch, not all tickets that are under that deployment are picked up and as a result automations doesn't work for those tickets.

The manual check has shown that ticket keys are present in "Commits" tab in deployments, however under "Issues" they are not present. We are following git commit messages pattern that has issue key to be mandatory filled in.

Please share why it might happen, any assistance is appreciated.

[Theodora Boudale · Accepted solution]

Hi Vlad,

This is a bit difficult to troubleshoot without checking your repo's deployments.

You can create a ticket with the support team and provide the repo URL and the build number of such a deployment. If we have an open support ticket, the engineer working on your case will be able to access the repo, and troubleshooting should be faster. You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. Please make sure to provide the workspace URL of the workspace where this repo belongs to.

Otherwise, I would need some additional info so I can try to reproduce (I haven't been able to reproduce it so far, but I can try again with a setup that is similar to yours):

• Does the deployment step belong to a branch pipeline, a custom pipeline, a pull-requests pipeline, a tags pipeline, or the default pipeline?
• Is it a pipeline that runs automatically or do you trigger it manually?
• Were there any other deployments to that environment, before the problematic deployment?
• How many commits show in the "Commits" tab in deployments?
• Are there issue keys in all commits or only some?
• You mentioned that ticket keys are present in "Commits" tab in deployments. Do these ticket keys also show as links to the respective Jira issues?

It is also not clear what you mean by "automations doesn't work for those tickets". What kind of automations do you have that do not work when this problem occurs?

Kind regards,
Theodora