1. 4/28/2017
JIRA Demonstration

2. How does CBIIT use JIRA (10 min) JIRA Demo (35 min)
Agenda
What is JIRA (5 min)
Who uses JIRA (5 min)
How does CBIIT use JIRA (10 min)
JIRA Demo (35 min)
Questions and Documentation

3. What is JIRA
JIRA is an issue management tool, a project management tool, a process management tool, and a project transparency tool

4. Issue Management
Objects in JIRA are called “Issues”. Issues represent work requests that need to be performed.
Issues types include – Bugs, Improvements, New Features, and Tasks
Issues operate based on a predefined workflow, which ensures that all issues are managed effectively.
Each issue has a status, which indicates where the issue currently is in its lifecycle.
Issues are housed within a project, and different projects may support different issue types.

5. Project Management
In addition to Issue Management, JIRA also supports Agile Project Management through the Agile tab at the top of the page, which gives you access to the Planning Board.
The Planning Board is a view of the JIRA issues that helps track progress. Issues are represented as cards, colour-coded according to issue type. Issues can be created, scheduled, and prioritized through the Planning Board.

6. Who Uses JIRA JIRA has several target communities at CBIIT, including:
Product users, who can log bugs and feature requests
Project managers, who can manage their projects and understand their team’s capacity
Developers, who can log issues, resolve issues, and execute stories
Testers, who can log issues and verify issue resolutions
Program managers, who will be able to see reports across projects to understand how effectively CBIIT is resolving issues

7. How will CBIIT use JIRA – Users
In order to create an issue in JIRA, you must have a user account.
If you are an ESN user, your account has already been migrated into JIRA.
If you are not an ESN user, you must create a new account.
Accounts entitle you to log issues, but not to manage or resolve issues.
To resolve an issue, you must be associated to a project.

8. Public Service Announcement – Creating JIRA Projects
It is imperative before you create a project in JIRA that you coordinate with the ESN/CBIIT project team.
In most cases, there should be only one project for a given product.

9. Creating a Project in JIRA
You can create a project in JIRA by logging a create project request in the CCB project.
PSA #2: Please be sure you coordinate this activity with ESN/CBIIT teams, so that (generally) there is only one project per product.

10. Creating a Project in JIRA Project Configurations
There are two primary choices that need to be made when creating a JIRA project:
Security Level – Open or Closed
Issue Assignment – Default Assigned or Default Unassigned
Security
Open projects are transparent to any JIRA users. Most projects should be Open.
Closed projects are visible only to Project Members.
Issue Assignment Defaults
Issue assignment defaults define what happens to an issue when it is first created.
Default Assigned projects assign all new issues to the project administrator, who then triages the issues and assigns them out
Default Unassigned projects leave new issues in a pool that can be picked up by anyone

11. Creating a Project in JIRA Associating Users with Projects
When a project is created, the Project Owner has the ability to associate users to a project.
One way JIRA is not like GForge
In GForge, users requested association with a project so that they can see information.
In JIRA, most projects will be “open”, so unless you need to resolve or test issues, you do not need to be associated with a project.
When a user is associated with a project, it means that they are assigned a role on the project, either as a developer, a tester, or a project administrator.
Project Administrators associate users with their projects. If you would like to be associated with a project, contact that project’s PM

12. Associating Users with Projects JIRA User Types
When a user is associated with a project, they can play one or more of the following roles:
Project Administrator – Power to modify project parameters once a project is created, including
Add or modify project users and project user types
Edit project components (lists of values for project specific fields like version)
Edit issue originator/Reporter
Developer – Able to create, modify, assign, and resolve issues
Tester – Able to create, modify, assign, and verify resolutions for issues

13. How to manage issues in JIRA CBIIT Workflow
CBIIT has custom configured a workflow to support issue management.
4) Demonstration - How you use JIRA
- Creating a user account (5 minutes)
- ESN users migrated
- Others can create by going to tracker.nci.nih.gov
- Requesting new projects (5 minutes)
- Requesting data migrations (5 minutes)
- Adding users to a project (5 minutes)
- Logging issues (5 minutes)
- Moving issues through workflow (15 minutes)
Demo

14. JIRA Documentation
CBIIT JIRA Configuration -
CBIIT JIRA Wiki and FAQ -
Release notes -
JIRA Users Guide -
Greenhopper 101 Guide -
FishEye Users Guide -

15. Acknowledgements Roxanne Martinez – JIRA Administrator
Doug Hosier – JIRA Administrator
Anand Basu – JIRA PM
Aynur Abdurazik – JIRA Test Lead
Byron Katz – JIRA Tester
Leslie Derr - Stakeholder
Cliff Wong – Stakeholder
Steve Lustbader - Stakeholder
Steve Matyas - Stakeholder
Miguel Buddle - Stakeholder
Shine Jacob - Stakeholder
Sichen Liu - Stakeholder
Steve Saksa - Stakeholder
Mohammad Farid - Stakeholder
David Mulvihill - Stakeholder
Kevin Hurley - Stakeholder
Satish Patel - Stakeholder