Doubts with linking GitHub and Jira Project for identifying commits that complete a task

Jaime Arturo
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 9, 2024

Are we obligated to create branch with the issue key and then commit with the issue key? Or can we just commit with the issue key assuming that branches have already been created?.


I'm aware I can easily experiment with this doubt I have but I'd rather hear from people who already have experience with this software.

1 answer

0 votes
Craig Nodwell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 9, 2024

Hi @Jaime Arturo welcome to the community.  You should always create a feature branch for your issue, unless of course you already have a working branch for that issue.  The point of putting the jira id into the commit is that build/deployment tools read the commit change log from git and pick the issue keys from that and not the branch not the pull request the commit.  There's no enforcement (unless it's internal to your organization) that you must commit on a specific branch, you can commit anywhere you have permission to with your Jira ID in the commit and the system will pick it up.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events