Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
TAGS
AUG Leaders

Atlassian Community Events