Jira hierarchy

Epic → An epic is crafted to represent the problem brought forth by the client for resolution. Subsequently, it undergoes refinement and is divided into smaller, manageable pieces.

Story → After the epic goes through technical and business discovery, it is decomposed into smaller pieces, known as stories, which are then inserted into the sprint.

It's important to note that an individual story may not necessarily resolve the problem brought forth by the epic. Instead, the story needs to be further broken down into smaller, more manageable pieces that allow for incremental delivery. This partitioning enables a step-by-step approach to addressing the larger problem and ensures that each story contributes towards its eventual resolution.

Bug → Jira ticket type used to register a problem found on QA or Prod environment.

Design → Created to design teamwork to solve the problem by a design perspective. They work on design activity on Sprint-1 of refinement/development.

Impediment → This type of ticket is created to register a block from outside of the dedicated team. Ex: Salesforce body change.

Sub-task → Throughout the refinement process, the developers divide the stories into smaller, granular components, which serve as valuable references for estimating effort during the planning meeting.

Sub-Bug → this ticket is created when our QA finds a problem during the test phase and is used to keep on track of what needs to be fixed to consider the story as DEVELOPED.