atlassian / atlassian/github-for-jira

Branches not linked to JIRA ticket via Branch Commit Messages

Open
#672 5 comments 1 reaction 0 assignees View on GitHub
enhancement stay tuned
Dominant language
No language data
Stars
655
Forks
194
PR merge metrics
No merged PRs in 30d

Description

Right now unless you name you branch with the issue name it won't show in the development pane even if there are commits with the ticket name, though the commits will show. However if you force a sync the branch will show up, is this a normal behaviour?

Steps to reproduce:

1. Create a issue in jira (e.g.: **JIRA-1**)
2. Create a branch in your repo (`my_feature`)
3. Change the **README.md** and commit message with "**JIRA-1 update README**"
4. The the commit will show in **JIRA-1** issue in Jira but not the branch `my_feature`.
5. Go to the My Applications -> Github and force a sync
6. The branch `my_feature` now shows up

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the README.md reproduction using a branch named my_feature and a commit containing JIRA-1, then compare the development pane before and after My Applications -> Github force sync. Determine whether branch linking is expected to occur from commit messages without a sync, and document or correct the behavior if it is not.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github
Domain
backend-api-design
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.