I’m working with an integrated setup where JIRA and Bitbucket are connected. This lets me create branches directly from JIRA tickets and navigate back to the tickets from the repository.
What I need: A way to generate a report showing which JIRA tickets were finished between two specific Git tags.
Example scenario: If I have release tag v2.1.0 as my starting point and v2.1.8 as my endpoint, multiple commits were made to complete several JIRA tickets like PROJ-2001, PROJ-2002, and PROJ-2003. I want to get a list showing these three tickets that were worked on during this release cycle.
Has anyone found a plugin or add-on that can handle this type of reporting? What would be the best way to tackle this requirement?
You can pull this data using the Bitbucket API in conjunction with JIRA’s REST API. Start by running the command git log v2.1.0..v2.1.8 --oneline --grep="PROJ-" to retrieve the commits between your specific release tags. From there, apply regex to extract the JIRA ticket IDs from the commit messages. Next, query JIRA’s API to check the status of these tickets and filter for those that are completed. I’ve implemented a similar approach, and it effectively automates the reporting process.
bitbucket’s smart commits rly simplifies this. just include ticket numbers in ur commit msgs and they’ll auto-link. then leverage jIRA’s version/fixversion fields to see wch tickets got fixed in each release. makes it way less tedious than parsing git logs manually.
Had this exact problem managing releases across multiple teams. Manual methods work but they’re painfully slow and you’ll mess up constantly.
Game changer was building an automated workflow for the whole thing. Set up monitoring on both Git repos and JIRA that auto-correlates commits between tags with their tickets.
It grabs commit data between whatever tags you want, pulls ticket IDs from commit messages, hits JIRA to check completion status, and spits out a clean report with everything you need. Done with manual Git log parsing and API scripts.
Runs on schedule or whenever you want it, so you get instant reports for any release. Way better than hoping teams remember to update Fix Version fields.
I use Latenode since it handles Git and JIRA APIs without hassle, plus the visual builder makes tweaks easy when things change.
Try using JQL with deployment tracking. If your teams link branches to tickets through Bitbucket integration, you can build a custom filter that combines date ranges with Git activity. Set up a webhook to update a custom field whenever commits happen between specific tags. I’ve seen teams use the Scriptrunner add-on for this - it monitors Git tag creation and automatically updates ticket fields with release info. Takes some setup work upfront, but you’ll get real-time visibility into which tickets belong to any release window. No more manual version field updates.
JIRA’s Release Notes feature sounds perfect for this. Set up your project with Fix Version fields, and it’ll auto-generate notes showing all completed tickets for each version. Just make sure your team actually updates the Fix Version field when they resolve tickets. I’ve found this way more reliable than trying to parse commit messages later - especially with hotfixes or cherry-picked commits that don’t follow the normal tag order. You can find it under Project Settings > Release Notes, and it exports to CSV if you need to process it further.