Can JIRA be linked to Mercurial without using Fisheye?

Hey everyone,

I’m in the process of setting up a dev server and I’ve chosen JIRA for tracking issues and Mercurial for source control. I’m wondering if there’s a way to connect commit messages to JIRA issues without having to shell out for Fisheye or other paid tools.

Has anyone figured out a workaround for this? I’d love to hear about any free solutions or DIY methods you’ve used. It would be super helpful to have some kind of integration between the two systems, even if it’s not as fancy as what Fisheye offers.

Thanks in advance for any tips or suggestions!

Indeed, linking JIRA and Mercurial without Fisheye is feasible. We implemented a custom integration using JIRA’s REST API and Mercurial hooks. It required some development effort, but it’s cost-effective and tailored to our workflow. The hook script extracts issue keys from commit messages and updates JIRA tickets accordingly. It also adds commit links to the issue, enhancing traceability. While it lacks some advanced features of Fisheye, it covers our core needs. Consider your team’s requirements and available resources before deciding on this approach. It’s a viable solution if you’re comfortable with a bit of coding and API integration.

yea, u can link jira and mercurial without fisheye. we use a simple hook script that parses commit messages for issue keys and updates jira automatically. it’s not fancy but gets the job done. just need some basic scripting skills to set it up. lemme know if u want more details

I’ve been using a combination of JIRA and Mercurial for a while now, and I can confirm that you don’t need Fisheye for basic integration. We developed a custom solution using Mercurial’s hook system and JIRA’s REST API. It wasn’t too complicated to set up.

Our approach involves a pre-commit hook that checks for JIRA issue keys in the commit message. If found, it validates the issue exists and is in the correct state. Post-commit, we have another hook that updates the JIRA issue with the commit details.

One challenge we faced was handling merge commits, but we solved it by adding some logic to our script. It’s not perfect, but it serves our needs well. The main advantage is the flexibility - we can tweak it as our workflow evolves.

If you’re comfortable with a bit of Python or shell scripting, this method could work well for you. Just be prepared to maintain it yourself as your needs change.