Thoughts on measuring feature-based support (Jira) Edited

Hi all!

I've been working on a way to measure production support related to specific feature releases from the info we have in Jira. We have a general production support epic, but I'm leading an effort to reduce instability introduced by feature releases and as such want to measure our progress. Right now, I'm having the team use project-specific labels they apply to production support issues introduced by that feature release. I then have a Google spreadsheet where I pull in number of tickets with those labels, number with critical/blocker status, estimated man-hours to resolve. I line that up with the feature epic, number of issues in the feature epic, and time it took to complete the feature as a proxy for the size of the release. 

As you can see, there's a lot of manual processes in there. I've been looking around on how to build custom reporting in Jira to try to automate this but from what I've found, most require dev resources which I'm trying to avoid. Any thoughts? Thanks!

0 comments

Comment

Log in or Sign up to comment
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

35 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you