Bug tracking, issue tracking, & project management tool
Download Full Article
Over 5,500 organizations large and small have streamlined their work practices with JIRA, the professional issue tracker and project management tool. Its usability and flexibility make JIRA a powerful solution to many scenarios
It’s a breeze to create tasks, bug reports, feature, requests, help-desk tickets, issues…anything. Attach files and add screenshots to issues too.
Find precisely what you’re looking for in seconds.
Charts, graphs, calendar pages…Real-time, relevant information in a convenient format.
Security and Permissions:
Fine-grained enterprise-level security.Permissioning schemes for users, teams and projects roles.
Receive the information you need, when you need it via email and RSS feed.
Workflow and Roadmaps:
Create workflows that map an issue’s lifecycle according to your business processes. View the project roadmap that’s automatically generated in JIRA.
Organise, Track and Manage:
Keep your projects and issues aligned.
Ease of Use:
A powerful, intuitive, web-based interface designed with business and technical users in mind.
A low maintenance system with straight forward administration capabilities.
Customise, Integrate and Extend:
Customise it to best suit your business needs. Enhance it by visiting the plug in library. Extend to web services with programmatic control (Revision Control Integration, SOAP,XML-RPC, REST and additional remote interfaces).
Different organisations use JIRA to track different kinds of issues. 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. A JIRA issue typically looks like this:
The numbered fields shown in the above screenshot are:
Key — a unique identifier for this issue.
Type — ( Bug, Improvement, NewFeature,Task,CustomIssue )
Status – the stage the issue is currently at in its lifecycle (‘workflow’).(eg: Open, In Progress, Resolved,Re-Open, Closed)
Resolution — a record of the issue’s resolution (Fixed, Won’t Fix, Duplicate,Can’t Reproduce)
Priority — the importance of the issue in relation to other issues. (Blocker, Critical, Major, Miner, Trivial )
Assignee — the person to whom the issue is currently assigned.
Reporter — the person who entered the issue into the system.
Project — the ‘parent’ project to which the issue belongs.
a. Component(s) (if applicable) — project component(s) to which this issue relates.
b. Affects Version(s) (if applicable) — project version(s) for which the issue is (or was) manifesting.
c. Fix Version(s) (if applicable) — project version(s) for which the issue was (or will be) fixed.
9. Summary — a brief one-line summary of the issue.
Environment (if applicable) — the hardware or software environment to which the issue relates.
Description — a detailed description of the issue.
Comments — added by people who are working on the issue.
Additionally, if your administrator has enabled ‘Time-Tracking’, the following fields will appear above the ‘Description’ field:
Original Estimate — the total amount of time required to resolve the issue, as estimated when the issue was created. (This field cannot be modified once work has been logged on the issue.)
Remaining Estimate — the remaining amount of time required to resolve the issue. This field only appears when work has been logged on the issue.
Time Spent — the sum of all the individual work logs for this issue. This field only appears when work has been logged on the issue.
A JIRA project is a collection of issues, and is defined according to your organisation’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 web enhancement request system
To see a quick snapshot of a project, click ‘Browse Project’ in JIRA’s main menu bar, then select the project of interest. The ‘Open Issues’ report will be displayed as shown below, showing a summary of the project’s components and versions — click on the component or version to see a list of all issues belonging to that component/version.
Every issue belongs to a project. Each project has a name (e.g. Website Issues) and a key (eg. WEB). The project key becomes the first part of that project’s issue keys, e.g. WEB-101, WEB-102, etc:
What is a component?
A project component is a logical grouping of issues within a project. Each project may consist of various components (or none), depending on your organization’s needs.
For example, a software development project could consist of components called ‘Documentation’, ‘Backend’, ‘Email Subsystem’, ‘GUI’.
A website enhancement request system might consist of components called ‘Products’, ‘Contact Us’, etc:
What is a version?
For some types of projects, particularly software development, it is useful to be able to associate an issue with a particular project version (e.g. 1.0 beta, 1.0, 1.2, 2.0).
Issues have two fields that relate to versions:
Affects Version(s) – this is the version(s) in which the issue is manifesting. For instance, a software bug might affect versions 1.1 and 1.2.
Fix Version(s) – this is the version(s) in which the issue was (or will be) fixed. For instance, the bug affecting versions 1.1 and 1.2 might be fixed in version 2.0. Note that issues which do not have a Fix Version are classified as ‘Unscheduled’, as shown in the screenshot above.
Workflow is the movement of an issue through various Statuses during its lifecycle.
JIRA’s default workflow looks like this:
A JIRA workflow is the set of steps and transitions an issue goes through during its lifecycle. Workflows typically represent business processes.
All editions of JIRA are shipped with one default workflow. The default workflow cannot be edited, but in JIRA Enterprise and Professional editions you can customise the issue lifecycle by creating additional workflows:
Exploring the JIRA workspace
The Dashboard is the first page you see when you login to JIRA. It has three areas:
The navigation bar (at the top of the screen) — this is the same on every page in JIRA. It contains links which give you quick access to many of
JIRA’s most useful functions.
The name of your JIRA system (e.g. ‘My Company’s JIRA’) — this area can also contain a ‘welcome’ message from your JIRA administrator.
The main area of the screen, below the top navigation bar — this area can be customized to display many different types of
Creating an Issue
To create a new JIRA issue:
1. Click the ‘Create New Issue’ link at the top of the screen.
2. The ‘Step 1. Choose the project and issue type’ screen will be displayed. Select the relevant project and issue type, then click the ‘Next’ button.
3. ‘Step 2. Enter the details of the issue’ screen will be displayed. Type a summary of the issue and complete any other required fields, which are italicised and highlighted by an asterix.
4. Click the ‘Create’ button at the bottom of the page. The new issue will be created and you will see the ‘View Issue’ screen, showing the issue details that you have provided. You may also receive an email containing details and a link to your new issue.
To see a list of all issues that you have created, which have not yet been resolved, go to the Dashboard and click the ‘My Unresolved Reported Issues’ link.
Attaching a Screenshot
JIRA allows you to attach screenshots you have captured to an issue
To attach a screenshot:
1. Open the JIRA issue that you wish to attach a screenshot to. Click the ‘Attach screenshot to this issue’ link in the ‘Operations’ menu.
2. The ‘Attach Screenshot’ page will open in a new browser window.
3. Ensure that you have captured an image to your operating system’s clipboard and click the ‘Paste’ button to paste the image. Your captured image should display in the blank area above
4. Enter a file name for the screenshot you are attaching in the ‘File name:’ field. The file name will be initially defaulted to ‘screenshot-1′.
5. Click the ‘Attach’ button to attach the captured image to your JIRA issue.
Searching and Reporting
JIRA provides a powerful issue search facility. The utility of this is further enhanced by the ability to save a search for use at a later time. A saved search is called an issue filter.
Searching for issues
On the top navigation bar, click on the ‘Find Issues’ tab. This will display the Issue Navigator on the right-hand side of the page, while the left-hand side of the page will display the following search form:
2.Type your search term(s) into the ‘Query’ box (see Query Syntax for help with this), and/or select other criteria from the drop-down boxes and check-boxes. The drop-down boxes and check-boxes allow you to narrow your search, be it to issues in a certain project, only issues that are marked as ‘stoppers’, only issues marked as ‘enhancements’, only issues reported by or assigned to a particular person, and so on.
3.Click the “View” button to perform the search and keep the search form visible; or click the “View & Hide” button to perform the search and hide the search form.
Using the Issue Navigator
The Issue Navigator displays the search results from an issue filter or from a Quick Search.
Viewing and exporting search results The search results are presented in a number of different formats (called ‘views’). To change views, simply select one of the links under Current View:
The different views are Browser, XML, RSS, Word, Excel, Chart
JIRA displays statistics for particular people, projects, versions, or other fields within issues. You can: Browse a project, a component or a version. Browsing uses the Issue Navigator to display a list of issues, which you can export in a variety of report formats (e.g. Microsoft Word and Excel).
RoadMap – JIRA provides a Road Map for each project, which shows issues scheduled for the next three unreleased versions. Road Map provide an overview of progress made towards releasing a version.
Change Log – Shows resolved issues for the previous three versions of a project.
Download Full Article