nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

jira linking to bamboo

Shaunt Kojabash

Hi - I have a question about jira issues and the application link works between jira and bamboo and stash. If I create a feature branch from within a jira issue - I see the branches, builds, and pull request info... however, when we deployed to an environment we don't see the "deployed to environment" unless we tag the issue key in the commit message. Is this still a needed step even if you create the branch out of the jira issue? Seems like the link should already be established but I'm not quite sure how it works. See attached screenshot.

I'm on version - 6.3.3

Any help would be greatly appreciated!

Accepted answers

Shaunt Kojabash

Ok - I would have thought that this would be automatic based on the fact that you create the link at the time you use JIRA to create the branch. Are you sure this is the case? This seems odd to me that I would need to do both.

All comments

Shaunt Kojabash

jira.jpg

ThiagoBomfim

Hi Shaunt,

Inserting the JIRA issue key in the commit message is something you have to do besides doing that to the branch name. That's how Stash is able to generate links, as well for example, as described in the document below:

JIRA Integration - Stash

Let us know if any questions.

Best regards,
Thiago Bomfim
Atlassian Support

Shaunt Kojabash

ThiagoBomfim

Hi Shaunt, I am sure that is the case. If you want to link a branch to a JIRA issue, you have to have the JIRA issue key on the branch name. The same is valid for a commit or for a Pul Request. Those are independent ways to link those entities to a certain JIRA issue. The way you are putting is that all commits under a certain branch that contains a JIRA issue key should be considered belonging to that JIRA issue key. That is not the case for many use cases you have in Git. If you ever decide, for instance, to merge master into that, every commit in your repo would be referenced to that JIRA issue key - which wouldn't be correct. I hope that answers your question.

Shaunt Kojabash

I see what you are saying... thank you. That was very helpful.

Joshua Angolano

Are there plans to change this in future versions? Seems like dual data entry. When the branch is already associated with the issue.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

bitbucket-server

bamboo

application-link