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.

...

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 Image ModifiedProgrammes orImage ModifiedProjects created in YPM (Yamaha Portfolio Board) . More detailed information about YPM setup can be found here: Jira training for Yamaha Portfolio Planning (YPM).
AnImage Modified 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

AnImage ModifiedEpic is a large feature, that is broken down into its component Stories by a team.

AImage ModifiedStory is a feature that can be tested separately, and is part of an Epic.

AImage ModifiedSub-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:

AImage ModifiedBug is a broken feature found outside of sprint;

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

AImage ModifiedDefect is a broken feature found during UAT;

AImage ModifiedSpike is a Proof of Concept or other research required to prove the feasibility of a solution;

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

AnImage ModifiedIncident 

AImage Modified Support

For testing addon Xray is used, the following issue types exist. These are used solely by testers, to plan their work;

AImage ModifiedPrecondition 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;

AImage ModifiedTest describes a single test scenario;

AImage ModifiedTest Execution reports the execution of a Test;

AImage ModifiedSub Test Execution represents sub-task tests executions;

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

AImage ModifiedTest 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

• 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
  Image Added
  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 Image Modified button anywhere in Jira from the top bar.

Image Modified

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: Image Modified

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)

...