Paul René Jørgensen / Adresseavisen AS[paul.rene.jorgensen@adresseavisen.no]

GOJIRA

Version: 20100211

AgendaIntroduction

What is JIRA? JIRA Concepts

What's an issue?Features

Issue CreationVersionsComponentsReportingRoadmapsNotificationsSearchSchemes

Best PracticesGenericAdministrationProject SetupUsers, Groups & Roles

What is JIRA?

JIRA is a web toolUse it to prioritize, assign, track, discuss, report and watch issues / tasks

Very configurable and extendableYou can adapt it to your business processes

It maintains your historic data

Many uses..

Bugs / Change request trackingHelp-desk / Support / Customer ServiceProject ManagementTask TrackingRequirements ManagementWorkflow / Process Managment

Jira Concepts - projects, issues and sub-tasks

What's an issue?Everything is customizable, but make it an exception rather than the rule to make changes from the defaultBuilt in issue types bring you a long way

BugNew FeatureImprovementTask

Summary - An informative title will make your life easierDon't prioritize everything as a blocker

Blocker, Critical, Major, Minor, TrivialAssignee

The person responsible for progressReporter

The person responsible for follow upStatus

Resolution

Fixed, Won't fix, Duplicate, Incomplete, Cannot reproduceDescription

Put all the meat hereComments

Crucible for communication and documentation

Workflow

You may customize the workflow to meet the business needs

Example: Software development project

�Example: Help Desk

Issue Creation

Creating a task, support ticket, bug report, feature requst is very straight forwardYou may customize all the fields and types in an issueIssues may be created in two different ways

Web: Using a form on the webEmail: Sending an email to a POP-enabled email account

Versions and Releases

Affects VersionThis is the version that this issue is prevalent

Fix VersionThis is the version where the issue is resolved

Versions may be software releases, but can also be thought of as deadlines, sprints or ie. meetingsA version should be released when a deadline occurs. Issues without resolution could either be put back in the long tail or be moved into a future version

Components

Use components to group issues togetherA component may have a user that is auto assigned issues when they are createdGreatly improve the usefulness of reports

Reporting

RoadmapsEasy view of the progress of a version / milestone

Notifications

Email notification when an email make a transition from one status to the next

Eg. Open -> In Progress Notifications are fulle configurableSubscribe to periodical reports on issue status

SearchSearch in all fields, even in custom defined onesSearches can be saved, shared and used as filters

Schemes

By using user roles schemes can easily be shared between projectsSchemes

Notification SchemeControls who is notified when

Permission Scheme Controls who is allowed to do what

Other noteworthy features

Fine grained security system, even on the issue levelSupports work and time trackingHighly extensible with open API's and a ton of third party pluginsSource Code is available to commercial customers

BESTPRACTICES

Best Practices

Avoid complex configurationsUse naming conventions

Don't make everyone administrators!Use roles to delegate administration

Use Roles Minimizes the number of schemes necessary

Use the default workflow if possibleUse a staging server to test new configurationsDocument everything (Use Confluence)If you use custom fields

Limit the context and reuse

Who is responsible for whatWho Sys Admins JIRA AdminsWhy Knows the system better Knows the business betterWhat Manage system fields

(priorites, issue types, resolutions, status) Create projectsManage users/groupsDefine standardsApprove pluginsManage security

Manage workflowsManage components / versionsManage custom field valuesBulk operationsCreate shared filters, dashboards, group filter subscriptionsMaintain permissionsMaintain notifications

How Communicate well Train them well

Project Setup Best Practices (1)

Custom Fields Limit Context by Project / Issue Type Reuse fields (use project contexts) Don't put every custom field in a global context

It clutters the issue navigatorUnderstand the resolutions field

When an issue has a resolution field set, JIRA considers it closed. Affects filters and reports.Set resolution field ONLY when issue is considered closed

Project Setup Best Practices (2)

Determine Project StructureMany small projects (ie. one per product)

You can denote the product information on an issue in these various ways

Project name itself (J)Components field (J)Version field (J)Custom fields (S)Cascading select field (S)

Handled by: (J) - JIRA Admins, (S) - SysAdmin

Users, Groups & Roles Best Practices

Users sign up be themselvsJoins the jira-users group

Use groups to mimic the organizationUse roles to give individual users and/or groups permissions using permission schemesNever give a whole group permissions in a scheme, use roles instead. Only exception: jira-users group

Q&A - don't let anything stop you

http://www.atlassian.com/software/jira/docs