DoIT Shared Tools - JIRA - Overview
This document gives an overview of jira issues, email integration and provides resource links from Atlassian.
What's in a Name?
JIRA is a proprietary issue tracking product, developed by Atlassian. It provides bug tracking, issue tracking, and project management functions. Although normally styled JIRA, the product name is not an acronym, but a truncation of Gojira, the Japanese name for Godzilla. The name JIRA, itself, a reference to JIRA's main competitor, Bugzilla. It has been developed since 2002.
The JIRA Project
A JIRA project is a collection of issues, and is defined according to your organization's requirements. For example, a JIRA project could be:
- a software development project
- a marketing campaign
- a helpdesk system
- a leave request management system
- a website enhancement request system
Every issue belongs to a project. Each Project has a Name and a Key. The Project Key becomes the first part of that Project's issue keys. In the image below, the Project name is Bucky's Training Software, the Project Key is BTS and the record number is BTS-1.
- The term "issue" is a legacy term from Jira when it was originally developed as a bug tracking tool designed and used strictly by developers. DoIT Jira Admins refer to an "issue" as one of a number of Jira delivered issue types like Bug, Improvement, New Feature, Task, etc.
- Different parts of the DoIT and the University use JIRA to track different kinds of issues. Depending on how your department is using JIRA, an issue could represent a software bug, a project task, a helpdesk ticket, a leave request form, etc.
- Issue types vary depending on your JIRA project's scheme. The image below shows 5 issue types and their definitions. Each Issue type has it's own distinct workflow.
- For a description of each field in an Issue, please refer to this part of the JIRA User's Guide, https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html.
- Custom issue types can be created upon customer request. JIRA Admins, please email email@example.com with:
- Your JIRA Project Name
- The name(s) of the Issue Type(s) you would like added to your Project.
- Whether or not you want this Issue Type to be the default Issue Type (e.g. it will be the first Issue type to appear in the Issue Type field)
In the image below, you will see 5 issue types in our Demo JIRA project circled in red. Bug appears first because it is the default Issue type.
How do I find my issues once I have them?
- Click on 'Issues' in the top navigation bar to search for Issues. In the image below, the Issue drop down menu shows two options, Current Search or Search for issues.
- The Search for issues option creates Issue filters which can be saved and used again, referenced on Dashboards, marked as Favorites and shared among team your members. In the image below, you will see filter attributes such as Project, Type, Status, Assignee which, by default are set to "All". Click on the dropdown arrow on the appropriate filter to narrow your search The More dropdown menu will show you other fields in the JIRA record you may search on.
- For more about working with issues, please see the Jira User's Guide here, https://confluence.atlassian.com/jira064/working-with-an-issue-720416195.html
- A JIRA workflow is a set of statuses and transitions that an issue moves through during its lifecycle and typically represents existing processes within your project. The workflows can be as simple or as complex as you need them. When you create an issue, it will automatically be assigned a workflow and a status on that workflow. Where it can move to is defined by the transitions that exit that status.
- For more about workflows, please see the Jira User's Guide here, https://confluence.atlassian.com/jira064/configuring-workflow-720412524.html.