How To Use Jira

Linaro uses Jira to track projects and the work being done under them. This page details how the Toolchain Working Group works through this.

Issue Type Hierachy

Linaro uses several issue types to track projects. These issue types form a tree like structure, which allow you to see how individual tasks relate to the global picture. Different issue types belong to different projects, but the hierachy spans between projects.

The following sub-sections describe each issue type.

Epic Cards

Issue Type

Roadmap Card - Title begins with 'EPIC:'

Project

Linaro Roadmap - CARD

Owner

Project Management, Tech Leads, and TSC

Approver

TSC

Lifetime

Multiple iterations - forever

Purpose

Epic cards represent long term goals of the team. They may not have an end - for instance the GCC Performance Epic is unlikely to ever be closed. These cards are regularly reviewed by the TSC. Epics are implemented by multiple Roadmap Cards.

Useful links

Toolchain Working Group Epics

Roadmap Cards

Issue Type

Roadmap Card - Title does not begin with 'EPIC:'

Project

Linaro Roadmap - CARD

Owner

Project Management, Tech Leads, and OPSCOM

Approver

OPSCOM

Lifetime

One iteration, maybe two

Purpose

Roadmap Cards implement Epic cards. They represent the work we plan to do within an iteration to progress the parent epic. Roadmap cards are implemented by an equivalent Engineering Card in the appropriate Engineering project.

Useful links

Toolchain Working Group Roadmap Cards

Engineering Cards

Issue Type

Engineering Card - Title begins with 'ENG:'

Project

Toolchain Engineering - TCWG

Owner

Tech Lead and Project Management

Approver

Tech Lead

Lifetime

One iteration, maybe two

Purpose

There is a 1:1 mapping between Engineering Cards and Roadmap Cards. The Engineering Card contains no useful information. Engineering cards are implemented by many Blueprints

Useful links

Toolchain Working Group Engineering Cards

Blueprints

Issue Type

Blueprints

Project

Toolchain Engineering - TCWG

Owner

Tech Lead and Engineer

Approver

Tech Lead

Lifetime

One or two weeks, at most a month

Purpose

Blueprints represent units of engineering work. The aim is that you should be able to complete at least one blueprint a month. Engineers should move these cards to 'In Progress' whilst they are working on them, and report progress within the card. A blueprint may have many sub-tasks.

Useful links

Your Toolchain Working Group Open Blueprints
Toolchain WG Blueprints Board

Sub-Tasks

Issue Type

Sub-tasks

Project

Toolchain Engineering - TCWG

Owner

Engineer

Approver

Engineer

Lifetime

A day or two

Purpose

Sub-tasks represent the things you have to do to complete a blueprint. These are useful as memory aids for engineers, and are not used by the Tech Lead to monitor progress.

WorkingGroups/ToolChain/Process/Jira (last modified 2013-05-21 08:57:08)