I have recently switched to Jira for bug tracking and installed version 4.1. We use Git for version control, and I want to integrate the two. During my search, I found that the Git Integration Plugin for JIRA by BigBrassBand is widely recommended.
The issue is, the plugin only fully supports Jira 3.13.
Does anyone have tips for making this work or any workarounds?
Additionally, any advice on pre/post commit hooks with Jira/Git would be really appreciated!
Having dealt with similar integration issues, I’d suggest exploring alternative plugins compatible with Jira 4.1. The Atlassian Marketplace offers several options worth investigating. One that’s worked well for me is the ‘Git Integration for Jira’ by Bigbrassband, which has versions supporting newer Jira releases.
Regarding pre/post commit hooks, consider implementing a simple script that extracts Jira issue keys from commit messages and updates the corresponding tickets. This can be achieved using Jira’s REST API and a bit of scripting in your preferred language.
A key tip: Establish a clear commit message convention across your team. Something like ‘PROJ-123: Brief description’ ensures consistent tracking. It takes time to get everyone on board, but it’s crucial for seamless integration between Git and Jira.
I’ve been using Jira with Git for a while now, and I can relate to your integration challenges. While the BigBrassBand plugin is popular, it’s not the only option out there. Have you considered looking into Atlassian’s own ‘DVCS Connector’ plugin? It’s designed to work with newer Jira versions and supports Git integration quite well.
For pre/post commit hooks, I’ve found success using a custom script that updates Jira ticket statuses based on commit messages. It’s a bit of work to set up initially, but it greatly improves workflow tracking. You can use Jira’s REST API to update issues directly from your Git hooks.
One word of caution from experience: make sure your team agrees on a consistent commit message format that includes Jira ticket numbers. This consistency is crucial for any integration to work smoothly. It took us a few weeks of trial and error, but once we got it right, the productivity boost was significant.
hey laura, have u tried the ‘Git Integration for Jira’ by Bigbrassband? its got versions for newer Jira. for hooks, u can make a script to grab issue keys from commits and update jira tickets. just make sure ur team uses a standard commit format like ‘PROJ-123: description’. it helps alot with tracking n stuff.