JIRA basics PART 2!

 

In the previous post, (JIRA basics PART 1) we revealed the basics of how to perform some common tasks within JIRA, specifically for Developers, we talked about how to create a task within a board, how to log work into a ticket and how to change its state.

In this “PART 2”, we’ll see how to use reports to determine a team member’s current workload and use several JIRA reports to get some basic statistics for a project.

HOW TO DETERMINE A TEAM MEMBER’S WORKLOAD:

You are the team leader, and the developers are all working on different tasks. As with any project, new tasks arise and you are requested to assign them to your team and determine their completion dates. You need to know your team’s current workload so you can determine who to assign the new tasks to, as well as when the team will be capable of working on them.

An easy way to do so is using JIRA’s reports. On the left menu, you will find the “Reports” link. Under the “Forecast & Management” area, you’ll find the “User Workload Report” which you can use to determine a particular team member’s workload in terms of hours of task-work. You can also use the “Workload Pie Chart” report to look at the entire team’s workload in pie chart form.

jira3
You can use the “Workload Pie Chart” report to look at the entire team’s workload in pie chart form.

HOW TO GET BASIC STATISTICS ON A PROJECT:

Now, the project manager needs to report on the project status to the stakeholders. Fortunately, JIRA can also help with this. In the Reports section, you can use the “Createjira4d vs. Resolved Issues” Report to get a good idea of the status of your current tasks. The “Resolution Time” report will tell you how fast your team can solve issues and give you information you can use to determine feasible due dates for your project phases.

If you are managing an Agile project, you can use the “Burndown Chart” to see how effectively the time is being used. A healthy project should burn time proportionately to the resolution of issues and completion of tasks.

Other charts like the “Pie Chart” report will help you get a good idea of how many issues are in each state of the life cycle.

With these basic tools you can start on your own project easily. Your team will be able to create tasks and log their work so managers and team leaders can assess the progress on the project using JIRA’s built-in reports.

We’ve reached the end of this series of posts, and I hope you’ve found it as rewarding as I did. Keep in mind that this tutorial was very basic. JIRA has many more features to offer, and is flexible in ways we didn’t cover here for simplicity’s sake.

If you want more information about JIRA and other IT related consultations, write to us at info@fwpr.com or check out our site at www.fwpr.com

We’ll be glad to assist you! 

This article was written by Carlos Malavé, Fusionworks’ Senior Technical Consultant.

——————————————————————————————————————————————————

If you liked this article, and want to be notified of other publications, subscribe here: FusionBlog Subscribe

Fusionworks: experts in Microsoft GP, Microsoft CRM, Oracle Fusion Financials, Oracle EBS, Prophix, SAP Business Objects, Microsoft Power BI. 

Leave a Reply

Your email address will not be published. Required fields are marked *