We are seeing work being done that is not in Jira.  We would love to be able to pull these velocity numbers to see which developers are lowest on story points in a team so we can work with them to start putting all work in Jira. 

Hey, 19f4a52ce028! Yes, I'm quite aware of that. You sound like you have some experience with this. What would you need to overcome this obstacle? If you have ideas on how to do that, I'd be happy to hear them!

27e320b8e8f5 That's great - the problem with suggestions like this is that there's usually a lot of "red tape" that individuals in companies need to go through to get authorization to spend money on an add-on. If you can solve that problem, you'll be golden!

Hi, all!

For everybody looking for a solution for this, I can recommend our app Report Builder, available on the Atlassian Marketplace. It offers a powerful report editor to create these kinds of statistics with just a few clicks. They can easily be added to dashboards as well. Have a look below to see how those reports look like for the scenarios described here. If you have any questions, feel free to book a demo call for Report Builder here: https://actonic.de/appdemo. Disclaimer: I am the Product Marketing Manager for this app and work for the vendor Actonic.

How much Story Points are assigned to developer X?

How much Story Points are open for component Y?

How much Story Points are scheduled for Release Z?

i can onle agree with all the fomer comments - i just relaized that this basic feature doesn't exist in Jira.

Plus, the bug in the "Confluence Jira Macro" which can sum up the Time Tracks of Jira but  - unfortunately - doesn't pull the correct values from the Jira field Original Estimate . In other words: Jira shows correct values but doesn't sum and Confluence does sum but has no correct values due to the bug reported in 2014 - and considered low prio  ( CONFSERVER-32757 )

Insane, how is it possible I need to manually sum up Story Points, a critical KPI for any Agile Team.

Wow... this request was submitted 13 years ago and still nothing?

This is basic need and should have continued in Jira cloud.

Greetings esteemed keepers of the Jira realms! 🏰

As I, an intrepid explorer of the digital landscapes, stumbled upon a relic that has withstood the sands of time, I bring forth the legendary tale of the "Forgotten Feature Request of the Thirteen Cycles"! 📜✨

Behold, oh wise overseers of code and trackers of tasks, for 144 moons ago, a humble Jira enthusiast sent forth a missive into the ether—a request so profound, so avant-garde, that it transcends the boundaries of mere mortal comprehension. The plea was simple yet profound: a feature that could shake the very foundations of the digital dominion!

In the annals of time, as the seasons changed, technologies evolved, and memes rose and fell, the Feature Request lay dormant, untouched, unloved. It weathered countless upgrades, bug fixes, and UI makeovers, yet its essence remained unchanged—an eternal testament to perseverance and neglect.

Oh, valiant guardians of user feedback, as the Feature Request gathered digital dust, it became a symbol of endurance, an icon of persistence in the face of seemingly infinite ignorance. Alas, as the world turned, the Feature Request silently whispered, "Am I a joke to you?"

Picture, if you will, a Jira where this request springs forth like a phoenix from the ashes of neglect, a beacon of hope for all ignored pleas. As the Feature Request basks in its quixotic glory, it yearns for acknowledgment, for recognition, for the sweet embrace of implementation.

Let it be known, across the servers and databases, that this Feature Request has defied obsolescence, and its saga shall be sung by digital bards for generations to come. As the cosmic ballet continues, the Feature Request stands as a testimony to the eternal dance of desire and indifference.

So, noble Jira stewards, in the spirit of whimsy and futility, let the tale of the "Forgotten Feature Request of the Thirteen Cycles" echo through the corridors of code, a gentle reminder that, sometimes, even the most insignificant requests yearn for their moment in the spotlight. 🌌🚀

May you find it in your bug-fixing hearts to bestow upon it the attention it so fervently craves.

Yours in the dance of endless updates and unresolved dreams, A Traveler Through the Digital Ages 🌐🕰️

+1