Introduction

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:

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;

ATest Plan is a container for test cases, usually related to a single sprint;

B2C Issues overview

B2C uses the following Field configuration

• Field configuration for IS Development projects

B2C Specific Fields

• Type of work:  Field to track type of work activated for Issue type Story, Spike, Bug, Task, Incident
  
  Technical debt: Efforts spent on improving the codebase, enhancing its structure, refactoring, and optimizing it without adding new functionality. 
  New Development: Efforts dedicated to developing new features, functionalities, or significant enhancements. 
  Maintenance: Efforts involved in maintaining the system, which includes activities like routine updates, performance tuning, etcetera. 
  Bug Fixing: Efforts expended to identify and resolve defects or issues reported in the system.

Priorities

B2C Workflows

This project contains the following workflows.

B2C Issue creation

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.

B2C Incident creation via (SD)

A B2C Incident can automatically created via a SD issue when status is set to In Progress.

Via the workflow menu option Create B2C-Incident can be selected.
After selection automatically a B2C Incident issue will be created, with same Description as the SD Issue.
This means that CAB can now be skipped for Incidents/Bugs.
This option is only available for Consumer Applications team, not for Epam.

With this option many fields will be copied, like previously was done for CAB.
See below fields that will be copied/set:

Unfortunately it is not possible to copy all comments, but last comment and the comment entered in the comment screen that pops up if this transition is used will both be copied to the new B2C incident.

Original SD ticket will be transitioned to status Awaiting Development.

B2C Boards