Versions Compared

Old Version 5

changes.mady.by.user Mark Chadbourne

Saved on

compared with

New Version 6

changes.mady.by.user Jason Crocker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

What is JIRA? Why are we using it? What are its benefits and its main features?

JIRA is a web based application used for bug tracking and implementing agile practices for projects. We are using JIRA for project management and assignment tracking. The main features include the ability to create issues, or tasks for a project and assign them to people. The issue is created on the project for a specific version of the project. When a person works on the issue they can track their progress in JIRA and anyone who is watching that issue will get notified of its change. You can also break up the issues into sub-tasks to break apart a whole task making progress more visible. You can sort a bunch of issues into groups called epics, allowing for the total project to be broken up into smaller sections. It also generates a burndown chart for the project automatically which is useful for agile. 

Panel
titleTable of Contents
borderStylesolid

Table of Contents

Issue Types

What is an issue? Under each issue type - what is the purpose of each issue type? When should I use it/not use it? Describe their main differentiating attributes.

An issue is something that needs to be completed for the project. Issues take many forms, a few of them are bellow. 

Epics- Epics are an issue with a large scope. This is used to break up work on a project into smaller sections of issues. Epics can be used for sorting purposes, allowing you to sort issues into categories of work. Epics also allow you to create a group of issues to break up the project into smaller sections to be completed. You link other issues to the epic, thus organizing them under that epic. You should not use an epic to represent a single issue, but rather use epics for organization. 

Stories- Stories are a type of issue that has an end result, such as code or a mock up. Stories are used to create something for the project, they are one of the more common issues. You would use a story to complete work towards the next version of the project. A story has an epic link and acceptance criteria in addition to the attributes issues have.

Spikes- Spikes are an issue revolving around gathering requisite information for the project. Spikes can be used for training activities or to signify a need for new knowledge to move on or complete a section of work. Spikes have the same attributes as a story but also add a confluence page link.

Tasks- A task is simply something that needs to be done, it is representing a need for something to be made or done.

Bugs- A bug is a problem with previous work that impairs progress on the project. A bug like spikes and stories has an epic link, however it does not have a priority and it requires a time estimate for it. You would use a bug when something is found about the project that impairs progress and needs to be fixed. These are not new features but rather fixes of old things.

 

Workflows

Discuss the process of going through each of these main workflow steps and highlight key differences between item types in each.

Creating

Epics

- To create any issue you use the create button on the top bar this opens a window where you can select the type of issue.

Epics 

To create an epic you select it from the issue type menu and it will update the attributes fields with the necessary fields for an epic. 

Stories and Spikes

Tasks

Bugs

Updating

Resolving