This document provides an overview of the project management software JIRA and its capabilities. It introduces JIRA concepts like projects, components, versions and issues. It describes how to customize workflows and filters in JIRA. The document also explains how to use the GreenHopper extension to manage projects using agile methodologies through planning boards, task boards and contexts. Overall, the document serves as an introduction to using JIRA for issue tracking and project management.

1. JIRA FUNDAMENDALS
PMO
September 2011

2. Meet JIRA
Project Management and Issue Tracking are not
But JIRA makes them easier!
easy tasks

3. Meet JIRA
JIRA is advanced highly customizable issue tracking system
In JIRA you could
 customize workflows to any business
process
 perform integration with existing systems
to manage tasks, track activity and
deadlines
 add lots of plug-ins as you need to
expand it capabilities
All this makes JIRA a flexible project management tool where you can:
 track bugs for a single application
 manage software development for several products
 or run countless projects throughout your entire company

4. JIRA Over the World
 JIRA is used by over 14,500 customers in 122
countries
 JIRA is used by over 157 projects at SoftServe

5. Agenda
 Getting Started
 JIRA Issue Types
 Filters & Dashboards
 GreenHopper Extension

6. GETTING STARTED
 JIRA Concepts
 JIRA Structure
 Issues
 Components
 Versions
 JIRA Menus Overview

7. Issue Overview
 What is an Issue?
A lot of organizations use JIRA to track different kinds of issues.
Depending on how your organization is using JIRA, an issue could
represent:
o a software bug
o a project task
o a helpdesk ticket
o a product improvement
o a leave request from client
o etc
7

8. Project Overview
 What is a Project?
– Project is an entity in JIRA
– A JIRA Project is a collection of issues
– Every issue belongs to the Project
– Each project has Name and Key
– Project Key becomes the first part of that Issue Keys
8

9. Project & Issues: Example
Project: Web Design Application
(Key: WEB)
WEB -12 WEB -14
WEB -11 WEB -13 WEB -15
9

10. Components
 Components are sub-sections of a project, which are used to
group issues within a project into smaller parts
 Operations with components:
• Add — Create a new component under which issues can be classed
• Delete — Remove a component from a project
• Edit — Update/change the details of a particular component
• Select Default Assignee — Set the default assignee for issues
created in a particular component
10

11. Versions
 Versions are points-in-time for a project, which help to schedule
and organize releases / sprints
E.g.: numbers of application builds, number of Sprints or any
other points-in-time etc
 Each Version can have the following statuses:
– Released — a bundled package
– Unreleased — an open package
– Archived — a semi-transparent package
– Overdue — the release date is highlighted
11

12. JIRA Structure
Project 1 Project N
Project 2
…
Versions Versions Components Components
Issue Issue Issue
Issue
…
Issue Issue
… …
Issue Issue Issue

13. JIRA Menus Overview
Dashboards
Login
Projects
Issues
Agile
Administration
13

14. JIRA ISSUE TYPES
 Issue Types Overview
 Workflow
 Bug Issue Type Creation
 Typical Actions on Issues

15. Issue Types
 Issues  Sub-Issues
– Epic – Technical Task
– Story – Sub-Bug
– Bug
– Improvement
– Task
– New Feature
– Risk

16. Issue Type: Epic, Story
 Usage
– Describes project‘s SOW (scope of work) within
Requirements Management process
 Difference
– None (all fields are similar)
 Common
– States, Transitions and Workflow

17. Issue Type: Task, Technical Task
 Usage Technical Task
– Communicates the need to do generic work for the
project
“Design role-based
security approach”
 Specifics
– Technical Tasks can be associated with any ―parent‖ JIRA
issue type
– Task can represents any generic non user story related
activity
 Recommendation
– Makes the most sense when used together with Story
issue type

18. Issue Type: Bug, Sub-Bug
 Usage
– Describes the problem which impairs or prevents
functionality of the product
– Sub-Bug supports Agile best practices on scope
management
 Difference
– None (all fields are similar)
 Common
– States, Transitions and Workflow

19. Workflow Overview
 What is a Workflow?
Workflow is the movement (or Transition) of an Issue through
various Statuses during its lifecycle
Possible statuses: Possible transitions:
o Open o Start Progress
o In Progress o Stop Progress
o Resolved o Resolve
o Closed o Re-open
o Reopened o Resolve & Close
19

20. Issues Workflow
20

21. Bug Issue Type: Creation
 To create a new issue select
“Issues > Create Issue”
24

22. Bug Issue Type: Creation
 Project – the 'parent' project to which the issue belongs
 Issue Type – selected issue type (e.g.: Story, Bug, Task, etc)
25

23. Bug Issue Type: Creation
26

24. Typical Actions on Issues
 Create
 Edit
 Assign
 Comment
 Log Work
 Attach Files
 Move
 Link
 Clone
 Convert

25. FILTERS & DASHBOARDS
 Searching
 Simple
 Advanced
 Quick
 Filtering
 Dashboards

26. JIRA Capabilities
 JIRA has the following capabilities:
1. Simple, Advances & Quick
Search
2. Powerful Predefined and
Custom Filters
3. Issues Bulk Operations
4. Issues Navigators

27. JIRA Search
 Sometimes you just want to be able to get particular issue
 Other times you can’t remember what the issues was

28. Simple Search
 Performing a Simple Issue Search:
– Specifying a Query (searching through descriptive Fields)
– Searching particular Projects or Issue Types
– Using the 'Components/Versions' section
– Using the 'Issue Attributes' section
– Using the 'Dates and Times' section
– Using the 'Work Ratio' section
– Using the 'Custom Fields' section

29. Simple Search
 To search for Issues select
“Issues > Search for Issues”

30. Simple Search
Issue Navigator:
Simple Search

31. Advanced Search
 Advanced Search allows to use Structured Queries
 JIRA Query Language (JQL) gives some SQL-like statements
Examples:
 project = "TEST“
 status = open and priority = high and assignee = osavchyn
 project in (JRA,CONF) and fixVersion = "3.14“
 remainingEstimate > 4h order by priority
More details can be found here:
Advanced Search

32. Advanced Search

33. Advanced Search
Advanced Search:
Query area
Advanced Search:
History

34. Quick Search
 Quick Search box is located at the top right of the screen
 Quick Search has:
– Jumping to an Issue
– ‗Smart‘ Querying: searches with minimal typing
– Free-text searching
More details can be found here:
Quick Search

35. Issue Filters
 A saved Search is called an Issue Filter
With an issue filter you can:
– display the search results in the Issue Navigator
– display the search results in a report format
– display the search results in a Dashboard Gadget
– share the search with colleagues
– add another user's shared filter as a favorite

36. Issue Filters

37. Issue Filters
Saving Filter
Details
Filter
Summary

38. Recommended Filters
 Groups’ Sub-Tasks
Example:
o Technical Tasks per each developer
o Technical Tasks per each QC Engineer
 Bug Status
Example:
o Bugs per status and priority
o Bugs assigned to particular person

39. Dashboards
 'Dashboards' link
In Dashboard you can:
– Display different information, depending on interests
– Visualize information using charts
– Share information with team members and clients

40. Dashboards: Gadgets
 The information boxes on the Dashboard are called Gadgets
 Gadgets Categories:
– Charts
– Confluence
– JIRA
– Wallboard
– Other

41. Dashboards: Examples

42. GREENHOPPER EXTENSION
 GreenHopper Overview
 Contexts
 Agile Boards
 GreenHopper and Dashboard

43. Overview
 GreenHopper is a JIRA plug-in that
– adds a broad collection of agile project management capabilities to JIRA
– extends JIRA with powerful platform for agile development teams
– simplifies the planning and organization of tasks
– simplifies workflows and reporting for agile teams

44. Overview: Structure
GreenHopper
Dashboard Agile
Planning Task Chart Release
Board Board Board Board
Contexts

45. Planning Board: Controls
Context dropdown Page Views
Project dropdown Issue Creation
Board
Quick Filters Additional Tools
dropdown
Viewing Mode Search
dropdown
Viewing Mode
sub-dropdown

46. Contexts
Set the Context Name Sort Criteria
Context is a Jira saved filter applied to the GreenHopper, which allow to see issues from
the custom point of view
Assign Filter Highlight Criteria

47. Planning Board
Goal: Enable users to prioritize and schedule issues
Allow Project Managers/Scrum Masters to provide effective Sprint
Idea: Planning, in-place versions management and issue scheduling
 Add stories/tasks while planning
Actions:  Re-prioritize issues during release
 Create and manage Versions

48. Planning Board: Overview

49. Planning Board: Issue Views

50. Planning Board: Create an Issue
Issue Creation:
1. Click on “New Card” on Navigation bar
on any Agile board
2. Click the icon (which will appear
when you hover over the Issue
Type or Priority icons) and select “Add
Sub-task” from the drop-down menu.

51. Task Board
Goal: Provide users with visibility on the progress of ongoing versions
Allow team members to view issues assigned to them, manage their
Idea: statuses and progress
 Transit issues through states
Actions:  Log Work and add sub-issues
 Flagging

52. Task Board: Overview
Task Board View Filter and Log Work
Issues Transition Issues Creation
Issue Transition

53. GreenHopper and Dashboard
 GreenHopper information can be represented on Dashboards
using corresponding gadgets:
– Agile Gadget
– Card View
– Days Remaining
– Project Progress
– Hours Burndown Chart
– Task Board
– Etc

54. GreenHopper and Dashboard
Agile Gadget allows to view summaries of GreenHopper information directly on Dashboard

55. Thank You!