We’re using JIRA and it’s working great for us. We’ve got it set up nicely with Perforce right now. But we’re thinking about switching to Kiln for our version control.
The big question is: can we keep our JIRA setup if we move to Kiln? We really don’t want to lose that connection. It’s a deal-breaker if we can’t make it work.
Has anyone successfully linked Kiln and JIRA? What was your experience like? Any tips or things to watch out for? We’re a bit worried about making the switch if it means messing up our current workflow.
Thanks for any advice you can share!
I’ve been through a similar transition, moving from Perforce to Kiln while keeping JIRA in the mix. Good news - it’s definitely possible to connect Kiln and JIRA. We managed to set it up without too much hassle.
The integration isn’t as seamless as Perforce’s out-of-the-box solution, but it’s workable. We used Kiln’s API to create custom scripts that sync commit messages with JIRA issues. It took some initial setup time, but once it was running, it became pretty smooth.
One thing to watch out for is ensuring your team consistently uses JIRA issue keys in commit messages. This helps maintain traceability between code changes and tasks.
Overall, while there might be a slight learning curve, the benefits of Kiln (especially if you’re into Mercurial) can outweigh the initial integration challenges. Just be prepared for some tweaking to get your workflow just right.
yeah, it’s totally doable to connect kiln and jira. we did it at my company last year. took some fiddling with the api and webhooks, but it works great now. just make sure ur team uses jira keys in commits. it’s not perfect, but way better than losing jira integration. go for it!
I’ve successfully integrated Kiln with JIRA in my previous role. It’s certainly possible, though it requires some configuration. We used Kiln’s REST API to create a custom integration that linked commits to JIRA issues.
The process involved setting up webhooks in Kiln to trigger updates in JIRA when commits were pushed. We also implemented a pre-commit hook to enforce JIRA issue key inclusion in commit messages.
One challenge we faced was maintaining consistency in commit message formats across the team. We solved this by creating a commit template and educating everyone on its use.
While it took some effort to set up, the integration greatly improved our workflow tracking and issue management. The key is thorough planning and clear communication with your team during the transition.