Saturday, February 20, 2010

My first experience with JIRA

JIRA is a proprietary enterprise software product, developed by Atlassian, commonly used for bug tracking, issue tracking, and project management. Since I'm developing a " Workflow Management System" I hope to use Jira as the Bug tracking and issue tracking tool of my system and I started to read about JIRA. JIRA has released initially in October 12, 2004 and it is written in Java. JIRA, is not an acronym but rather a truncation of "Gojira" (the Japanese name for Godzilla) It has Proprietary License but free for noncommercial. I hope to get the free version of it :)


JIRA Concepts


Issue : (http://confluence.atlassian.com/pages/viewpage.action?pageId=185729613)

  • Depending on how your organisation is using JIRA, an issue could represent a software bug, a project task, a helpdesk ticket, a leave request form, etc. Key components of JIRA issue are as below. (As shown in the image above)
  • Key components of JIRA issue are as below. (As shown in the image above)
  1. Key — a unique identifier for this issue.
  2. Type — (Bug, Improvement, New Feature, Task ,Custom Issue)
  3. Status — the stage the issue is currently at in its lifecycle ('workflow'). (Open, In progress, Resolved, Reopened, Closed)
  4. Resolution — a record of the issue's resolution (if the issue has been resolved) (Fixed, Won’t Fixed, Duplicate, Incomplete, Cannot Reproduce)
  5. Priority — the importance of the issue in relation to other issues. (Blocked, critical, major, minor, trivial)
  6. Assignee — the person to whom the issue is currently assigned.
  7. Reporter — the person who entered the issue into the system.
  8. Project — the 'parent' project to which the issue belongs.
  9. Component(s) (if applicable) — project component(s) to which this issue relates.
  10. Affects Version(s) (if applicable) — project version(s) for which the issue is (or was) manifesting.
  11. Fix Version(s) (if applicable) — project version(s) for which the issue was (or will be) fixed.
  12. Summary — a brief one-line summary of the issue.
  13. Environment (if applicable) — the hardware or software environment to which the issue relates.
  14. Description — a detailed description of the issue.
  15. Comments — added by people who are working on the issue.

Project: (http://confluence.atlassian.com/pages/viewpage.action?pageId=185729449)

  • A project is a collection of issues:
  • Some Examples are
a software development project
a marketing campaign
a helpdesk system
a leave request management system
a website enhancement request system
  • Issue Example
Project Name : Web site project
Project Key : WEB
Issue keys : WEB 100, WEB 101, WEB103
  • A project component is a logical grouping of issues within a project. Each project may consist of various components (or none)
Project Name : Web site project
Project Key : WEB
Issue keys : WEB 100, WEB 101, WEB103
Components : Documentation', 'Backend', 'Email Subsystem', 'GUI'
Documentation Issues : WEB 100, WEB 101
Backend issues :WEB 103
  • Version : For some types of projects, particularly software development, it is useful to be able to associate an issue with a particular project version.Version can be in any of three states. (Released, Unreleased or Archived)

Workflow (http://confluence.atlassian.com/pages/viewpage.action?pageId=185729618)

  • Workflow is the movement of an issue through various Statuses during its lifecycle.

No comments:

Post a Comment