...

2. Jira YIS for development

Issuetypes

Image Added

Issuetypes have a hierarchy to them:

Items in YIS project build on the Programmes or Projects created in YPM. An Epic should always be linked to one of these, so it is clear which strategic initiative it's part of.

An Epic is a large feature, that is broken down into its component Stories by a scrum team.

A Story is a feature that can be tested separately, and is part of an Epic.

A Sub-task is an activity that needs to be performed to complete a higher-level issuetype. It's always part of another issuetype.

At the same level as Story, other Product Backlog Items exist with slightly different meanings:

A Bug is a broken feature found outside of sprint;

A Change Request is a change to an existing feature, requested during UAT;

A Defect is a broken feature found during UAT;

A Spike is a Proof of Concept or other research required to prove the feasibility of a solution;

A Task is a Non-Functional Requirement, work in software development that brings no value to business yet is necessary (for example: code refactoring).

For testing using addon Xray, the following issuetypes exist. These are used solely by testers, to plan their work:

A Precondition is ???

A Test describes a single test scenario;

A Test Execution reports the execution of a Test;

A Test Plan reports the execution of a Test Set???

A Test Set collects Tests that logically belong together.

...

Image Removed

Workflows

This project contains three workflows, with the distinction being made whether an item contains a software release (development workflow) or not (four step workflow).

...