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?
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events