...
Never worked with Jira before? No problem. Please first read the Jira training Basics page.
This chapter is part of is part Jira training for Information Systems, below the Jira setup for Information Systems - B2C Apps (B2C) is explained.
Documentation by EPAM for Jira usage can be found under: Jira Ticket Lifecycle
Project B2C is a Software delivery Project used by B2C and EPAM teams working Scrum or Kanban.
Issue types have a hierarchy to them:
Items in B2C Jira-project are build on the Programmes orProjects created in YPM (Yamaha Portfolio Board) . More detailed information about YPM setup can be found here: Jira training for Yamaha Portfolio Planning (YPM).
An Epic should always be linked to one of these, so it is clear which strategic initiative it's part of.
Explanation per issue type used in B2C
AnEpic is a large feature, that is broken down into its component Stories by a team.
AStory is a feature that can be tested separately, and is part of an Epic.
ASub-task is an activity that needs to be performed to complete a higher-level issue type. It's always part of another issue type.
At the same level as Story, other Product Backlog Items exist with slightly different meanings:
ABug
...
is a problem which impairs or prevents the functions of a feature.;
A Change Request is a change to an existing feature, requested
...
during UAT;
ASpike is a Proof of Concept or other research required to prove the feasibility of a solution;
ATask is a Non-Functional Requirement, work in software development that brings no value to business yet is necessary (for example: code refactoring);
AnIncident
A Support
For testing addon Xray is used, the following issue types exist. These are used solely by testers, to plan their work
...
;
...
ATest describes a single test scenario;
ATest Execution reports the execution of a Test;
...
A
...
Test Plan is a container for test cases, usually related to a single sprint;
...
B2C uses the following Field configuration
This project contains the following workflows.
Users (licensed user) can use the button anywhere in Jira from the top bar.
When using the create button the correct project and issue-type needs to be chosen and some other (required) fields as well. Required fields are marked with a red * .
Example:
Issues can also being created via the Board or backlog. Subtasks can being created via the original issue. Detailed instructions can be found in Jira training Basics - Issue Creation.
...