JIRA beginner in need of help - Scrum Project Management

[Michael Iberg]

Hello All,

I joined a new organization who uses JIRA to manage their portfolio of application development work, and this is the first time I have used JIRA.

I have been a scrum master and product owner in my previous organization so I am very comfortable with writing user stories, acceptance creria and working with the team(s) to issue storypoints/hours to each story. I am well versed in Microsoft TFS; which was the tool we used in my previous organization to build, test and deploy software, as well as build, refine and maintain product backlogs, assign Sprints etc. 

What I am trying to figure out with JIRA is, how do get the tool to produce burndown charts, velocity, etc, as well as what are my options for portfolio management? In the past, when I used TFS, this information seemed to be automagically generated as long as we had points/hours associated with the stories. This does not seem to be the case with JIRA.

If anyone in the community could point me in the right direction, it would e greatly appreciated!!!

Mike in STL Missouri

[Manon Soubies-Camy]

Hello @Michael Iberg and welcome to Community!

Charts are indeed automatically generated as long as story points/hours are associated with stories, see below links for further information:

• Jira Software: Reporting in Jira
• If you're on Cloud (i.e., your Jira URL looks like xxx.atlassian.net): Reporting
• If you're on Server: Reporting

Hope this helps,

- Manon

[Michael Iberg]

Hello @Manon Soubies-Camy,

Thank you for the response! The links you provided unfortunately are not the ones I need to solve my problem. I am thinking the reason why our instance of JIRA is not aggregating the hours/points info to display burndown, velocity, etc may have something to do with the overall workspace/project settings. 

The search continues....

Mike

[Manon Soubies-Camy]

Have you looked at the "Understand the xxx chart" sections? For example, for the burndown chart you can read here:

• The Burndown Chart is board-specific – that is, it will only include issues that match your board's saved filter.
• The Burndown Chart is based on your board's column mapping. An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board.

This may help you finding the issue :)