Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,491
Community Members
 
Community Events
184
Community Groups

No jira issue linked to pull request

Edited

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

1 answer

1 accepted

1 vote
Answer accepted
Esther Strom
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 25, 2021

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.  

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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 03, 2021

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

This was not very helpful.

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

  1. 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).
  2. 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)
  3. 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.

Like # people like this
Esther Strom
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 17, 2022

I don't have anything helpful to say about 1 and 3, but 2 is incorrect. You can connect multiple tickets to a single pull request by including all ticket numbers at the start of your commit message:

git commit -am "JIRA-123 JIRA-234 JIRA-345 link multiple tickets"  

(It's been a while since I've done this as I'm no longer a dev; you may need to comma-separate the ticket numbers, but I don't think so.) 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events