© 2015 cPrime Inc., All Rights Reserved

JIRA Administration Essentials

About cPrime

2

cPrime is an Alten Group Company

Class Prerequisites• Basic JIRA knowledge

• Create and edit Issues

• General Enterprise Tool Experience• Worked with other Enterprise tools since they are

often very similar

• Ability to research solutions and experiment• Look up potential solutions and apply them to your

instance

3

Class Overview• This basic JIRA administration class will help

you• Become more familiar with JIRA administration

elements and areas• Familiarize yourself with project configuration• Understand where global changes can be made• Understand JIRA Agile Board configuration• Learn where to find answers to common questions• Help you support your environment

• This class is not intended to• Cover all administration aspects of JIRA (there’s just too

much!)• Address every situation you may encounter• Teach you how to configure JIRA

4

Tracking Our Progress

5

T R O U B L E S H O O T I N G A N D B E S T P R A C T I C E S

J I R A G E N E R A L A M I N S T R AT I O N

W O R K F L O W E S S E N T I A L S

JIRA PROJECT ADMINISTRATIONRESOURCES

What is JIRA• JIRA is

• A virtual work planning and delivery tool• Customizable for your company and project needs• Provides transparency and real-time reporting

6

What can JIRA do for you?• JIRA can help you manage your projects

• Manage and hold all your projects in one location• Track and organize enterprise-wide initiatives• Follow team activity with real-time reporting• Monitor single or multiple projects• Provide visibility and transparency

• Projects help us align resources to collaboratively create a product

7

Product

JIRA Framework

8

Configuration Visualization and Utilization

Information

Agile Boards & DashboardsJIRA System Configuration

Searching & FiltersProject Configuration

Project Data

JIRA Administration

• Project Administration• Issues• Workflows• Roles• Versions• Notifications

• General Administration• Projects• Permissions• Add-ons

9

Administration

JIRA System Configuration

Project Configuration

Project Categories

Projects

Components (Work Categories) Versions (Releases)

Issues

Issue Type

Sub-Task

JIRA Issue Architecture

10

Sub-Task

Issue Type

Sub-Task Sub-Task

Definitions

11

Term Definition

Projects Collection of tasks with a common outcome

Project Categories Grouping of projects

Components Categorization of projects

Versions Releases (v1.0, v1.1, v2.0, etc)

Issues Describes work to be done

Issues Types Categorization of issue (Story, Bug, Request, etc)

Sub-Tasks Sub-steps required to complete an issue

JIRA Standard Issue Type Hierarchy

12

Epic

Story/ Bug

Sub-Task

Top

Middle

Bottom

JIRA Workflows

13

• JIRA uses a workflow to manage work states• Customized for team uses• Applied to projects and issue types

JIRA Ownership

14

• JIRA uses the concept of ownership:• System Admin – Owns administrative components• Project Lead – Manages The Setup of Environment• Component Lead – Manages the issues in a category• Issue Assignee – Does the work described in an Issue• Sub-Issue Assignee – Does the work in Sub-Issue

Projects deliver Products

15

IssuesIssuesIssuesIssues

Issues Workflow People

Project

Product

JIRA Projects

16

• What makes up a Project?• People working towards a common outcome: i.e. A

software product or a marketing project• A unique Project Key is created:

• External Website (Project Key = EXWEB)• Human Resources (Project Key = HR)

• This unique key is used to identify all issues• A Project Lead, manages the project

JIRA Project Configuration Options

17

• Projects select available configuration options• Issue Types• Workflows• Screens• Fields• Permissions• Notifications

• Projects create and define• Versions• Components• Roles

JIRA Schemes

18

• View and apply a configuration Scheme to a Project

• Scheme is a collection of configuration options• Issue Types Scheme – determines

what issues types the project will use

• Workflow Scheme - determines what workflow each issue type will follow

• Screen Scheme – determines what fields are available for each issue type

• Schemes are defined by Administrators and selected by Project Administrators

Issue Type Scheme

19

• View current project Issue Types and associated workflows

• Change to another available Issue Type scheme

Workflow Scheme

20

• View current Workflow and which Issue Types it applies to

• Switch Scheme to select another Workflow Scheme

Screen Scheme

21

• View current Screens and what operations and Issue Types they are associated with

• Switch Scheme to select another Screen Scheme

Field Configuration

22

• View current Fields and what Screens they are on

• Switch Configuration to use another Field Configuration Scheme

Screen and Field Relationship

23

Permission Scheme

24

• View current Project Permissions and how they are associated with Users, Groups, or Project Roles

• Switch Scheme to select another Permission Scheme

Notification Scheme

25

• Project team members can be notified of specific changes in the Project Switch Scheme to select another Permission Scheme

• Switch Scheme to select another Notification Scheme

What’s a Watcher

26

• Teams can become number to too many emails based on a Notification Scheme

• A Watcher is someone who signed up to received Notifications based on the Notification Scheme

• This allows users to “opt in” to project Notifications

Project Specific Configuration Options

27

• While Schemes are selected from available options, there are project-specific elements that can be configured• Versions (Releases)• Components• Roles

Versions

28

• Versions are project-specific Releases or Milestones

• Configure Version name, description, and dates

Components

29

• Components are project-specific categories• “Tag” an issue with a Component• Configure Version name, description, and

Assignee

Components

30

• Issues may belong to many or no components• Components have a Component Lead• The Project Lead can configure a Project to

assign all issues automatically to the Component Lead

Issues

Issues

Issues

Issues

Component 1

Issues

Component 2

Two Components

Roles

31

• Project roles are a flexible way to associate users and groups with a particular project

• Used in conjunction with Permission Schemes to define access and activity permissions to your project

• Other roles may be in your instance or be created to support organization needs

Default Project Role Definition

Administrator Usually associated with resources who administer the Project

Developer Usually associated with resources who work on and manage Issues

User Usually associated with resources who will view work

Roles

32

• Other roles may be in your instance or be created to support organization needs

Hierarchy of Roles

33

Admin

Developer

User

Inherit reduced permission roles

Demo

34

• Demo of your JIRA Instance• Project Configuration• Selected Schemes• Versions and Components• Roles and Permissions• Notifications

Questions?

35

Online Resources

36

Resource LocationJIRA Complete Administrators Guide https://confluence.atlassian.com/display/AGILE/

JIRA+Agile+Administrator%27s+Guide

JIRA User’s Guide https://confluence.atlassian.com/display/JIRA/JIRA+User's+Guide

JIRA Agile User’s Guide https://confluence.atlassian.com/display/AGILE/JIRA+Agile+User%27s+Guide

Configuring Workflows https://confluence.atlassian.com/display/JIRA/Configuring+Workflow

Thank you!

37