Are you using EPIC? You can track it on the "Backlog" view.
What version of JIRA Agile do you have? In your project overview page (e.g. myjira.com/browse/MYPROEJCT), open the "Overview" tab and click the "Agile" tab and play around with it and see if there's info you can use or maybe switch to the other tabs
Thank you for the suggestions. We are using JIRA 6.3.12. Epics was my first thought also, but the team is using Epics to track groupings of issues in yet another way. So, using Epics for this is not an option at this point. I have looked through all the existing reports for projects and Agile boards, and not found anything that will work. The team has over complicated their use of JIRA and dug themselves into a hole. I was hoping there was a built in report for this so I wouldn't have to advise them to restructure what they have done.
Hi @Trudy Claspill
I see from your other comment that you are on JIRA 6.3.12. So here is an option for you to consider.
Rather than using the Agile reports you can use a dashboard gadget that provides you with the ability to total values (such as https://marketplace.atlassian.com/plugins/com.eazybi.jira.plugins.eazybi-jira/server/overview) to calculate and then display the number of story points in each status. You could also use different filters to reflect different periods of time as well. There are of course lots of different ways of cutting this information up but at the end of the day it is not really setup to show you progress against story points over an extended period.
If you are using Releases you can look at a limited amount of information with the release burndown which will show last 5 sprints and future predictions... See https://confluence.atlassian.com/agile067/jira-agile-user-s-guide/using-a-board/using-reports/viewing-the-release-burndown for more detail.
Good luck with finding a solution.
Thanks, Phil, for the suggestions. The group does not appear to be using Releases in an appropriate way either. They have done some really weird things with their JIRA projects and agile boards, without having a good understanding of how JIRA works and without asking for help from the people with the expertise. :-( Trying to get them what they want at this point without restructuring is going to be very difficult and time consuming.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG