Hi team,
I find myself quite frustrated by a number of features in Jira that are 1 step short of being useful. My canonical example is velocity and capacity for scrum teams:
- The velocity report provides all the data for the last 7 sprints, but falls short of doing the calculation to determine a squads current velocity
- The squads velocity isn't displayed or present in any other part of the application where the information would be useful. For example when performing sprint planning there's no indication of the squads current velocity let alone factoring in capacity of the squad.
All the data is in Jira, and obviously these things can be produced manually, but computers don't exist for humans to perform manual tasks with them. This sort of stuff is super common in the industry, basically all scrum teams use these sorts of numbers every sprint. I guess I'd just like to see things like this have more priority as personally I think it would have a big impact on process friction and increase the value we get from the product. It seems very backward to have to jump into a spreadsheet all the time to do common things.
Do you have other issues like this, that seem like "doable quick wins" you'd like to highlight?
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Become an effective Jira admin
Manage global settings and shared configurations called schemes to achieve goals more quickly.
Streamline Jira administration with effective governance
Improve how you administer and maintain Jira and minimize clutter for users and administrators.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.