Let’s talk JIRA basics!

Let’s talk JIRA basics!

with No Comments

 

If you haven’t used JIRA yet, you’re missing out!

JIRA is the industry standard tool when it comes to Agile software development management and is the most widely used tool of its kind. JIRA undergoes constant improvement which has made it even more useful for project managers, team leaders and developers alike.

It’s got tons of cool stuff like code repository integration, new board types you can use for different types of projects (it’s not just for Agile anymore), and you can even link a lot of popular external applications such as Zendesk right into your profile.

However, in this two part series, we just wanted to go over the basics of how to perform some common tasks within JIRA.

For Developers, we’ll talk about how to create a task within a board, how to log work into a ticket and how to change its state.

HOW TO CREATE A TASK:

You’re the developer and are asked to code some new functionality for a project. The task needs to be documented so that it can be tracked and measured.

1 – Navigate to your project’s board

2 – On the top bar, hit the “CREATE” button on the right

3 – Just fill out the fields and hit Create!

jira1
Hit the “CREATE” button on the right

Make sure you give your ticket an intuitive name (using the summary field) and that you properly estimate its effort using the “Original Estimate” and “Remaining Estimate” fields.

jira2
Use the “Original Estimate” and “Remaining Estimate” fields.

For JIRA to yield useful information, we need to log our work into each ticket.

Here’s how to do so:

  • On the Kanban Board, click on the ticket you wish to update.
  • Then click on the … (ellipses) button on the upper right hand corner of the ticket details area.
  • Click on “Log Work
  • Enter time spent using WDH (Week-Day-Hour) nomenclature. For example, if you worked 2 and a half workdays on a task, you should enter it as 2d 4h.

Now the rest of the team is aware of how much time has been spent on this task. If you need to change the ticket status, just drag it to a different column on the Kanban Board.

So, we’ve gotten this far with PART 1 of the series “Let’s talk JIRA basics”, but there is still a bit more to cover and learn. So, don’t miss the next post if you want to find out exactly 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.

Meanwhile, if you need help or 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.

Check out “JIRA basics PART 2” for more useful information on JIRA!

—————————————————————————————————————————————————————————-

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. 

Share:

Leave a Reply