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; } } }

No jira issue linked to pull request

Bohdan_zvopor

Hi! How automatically linked Jira issues when making a pull request.? https://prnt.sc/10vatrg

I have made integration with jira https://prnt.sc/10vazyo But still no issues there

Accepted answers

Esther Strom

Hi, @Bohdan

The easiest way to create a link between a ticket and a pull request is to just set your branch's commit message to have the Jira ticket number be the first thing in the commit.

git commit -am "JIRA-123 this is my commit message"

This will result in a link from this commit/branch to the jira ticket called JIRA-123.

All comments

Esther Strom

Hi, @Bohdan

The easiest way to create a link between a ticket and a pull request is to just set your branch's commit message to have the Jira ticket number be the first thing in the commit.

git commit -am "JIRA-123 this is my commit message"

This will result in a link from this commit/branch to the jira ticket called JIRA-123.

devynfarr

Ok that's the easiest way. Are there other ways?

What if the commit message didn't include the proper ticket number, but I still want to create the link between the issue and the P/R?

So far the only solution I've come up with is creating another commit to the P/R branch simply to mention the ticket number. Kinda awkward.

Esther Strom

The full documentation on how development tools are linked to Jira tickets.

devynfarr

This was not very helpful.

The link states the following options for a P/R:

Include a commit in the pull request that has the issue key in the commit message. Note, the commit cannot be a merge commit (this is the dummy commit option i mentioned above).
Include the issue key at the beginning of the pull request title. (only works for 1 issue, and is misleading since a "forgotten" or "late addition" issue is likely a minor one in the context of the P/R, not worthy of being in the title)
Ensure that the source branch name also includes the issue key at the beginning of the branch name. (not something you'd change after the fact just to connect a missed jira issue)

These are all equally non-ideal options. Thankyou for digging up that document. I'll have to impress upon my team the seriousness of getting their commit messages right the first time.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

jira-cloud

atl-gruland

connect