Helping organizations improve how they deliver value for over 25 years. Using a mix of agile technical practices (XP), workflow design, and applied psychology/neuroscience.
If you want metrics out of Jira, the single most important thing you need to access is the issue history and it’s not obvious how to get that. Just about all the metrics you’ll want to collect will need data from the history - you might need to know when an item started or when it entered a certain priority or when the flag was set or cleared. In this second part on the Jira API, I dig into the issue history. How do you get it, what can you expect to find there and more interestingly, what's not there that you really need. https://lnkd.in/g-cuFBmY
Oliver Oyston
8mo
Great article! As for the casing consistency issue - it is whether the field is a core or custom field. The core ones start with a lowercase letter and the custom ones an uppercased letter. Confusingly, "agile" fields are implemented as custom fields and hence the discrepancy. I avoid the status category (typically, for boards) and infer the workflow from the board config. Then you just have to map legacy statuses. For projects and filters, I use the status categories as a starting point, but then allow more nuanced mapping.
Paul Rayner
8mo
This is so good! Thanks for doing this.
Senior Product Manager at Aha! — The world's #1 product development software
8moI really love the actionable agile plug in for jira it gets to the root of the data and has some clever insights.