Page History
...
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
B2C-Apps (B2C)
Project B2C is a Software delivery Project used by B2C and EPAM teams working Scrum or Kanban.
B2C Issue Types
Issue types have a hierarchy to them:
...
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 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;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;
...
For testing addon Xray is used, the following issue types exist. These are used solely by testers, to plan their work;A
Precondition describes the correct starting point of the test case. It can be a user's configuration; or a required object status, "with product _1" for example; or some permission that needs to be set before a test case is run;
A
Test describes a single test scenario;
A
Test Execution reports the execution of a Test;A
Sub Test Execution represents sub-task tests executions;
A
Test Plan is a container for test cases, usually related to a single sprint;
A
Test Set collects Tests that logically belong together, so they can easily be reused, for example for planning of UAT.
B2C Issues overview
B2C uses the following Field configuration
...
This project contains the following workflows.
B2C Issue creation
...
Overview
Content Tools