How to Report Magestore Product bug

Product Internal Service

Report Bug

Receive &

First Response

Analyst &

Diagnose &

First Plan

Weekly PlanningResolveRelease

In order to provide timely resolution on the most critical issues and pull requests, the Magestore Product team has implemented Severity/Priority concepts to our community driven projects.

This approach makes open-source collaboration more transparent for all participants. Having clear contribution rules in place helps to build clear expectations for Community Contributors and establish clear priorities for Community Maintainers and the Magestore team.

If you would like to contribute improvements or bug fixes to Magestore Product, and make sure it is valuable for the Community and Magestore as well, we highly recommend that Community Contributors to take issues from the backlog based on Priority. Magestore Product Team and Community Maintainers process contributions based on the issue/pull requests priority starting from P0, P1 to P4.

How to Report Magestore Product bug

Overview

Severity and Priority

SEVERITYDESCRIPTION

S0

- Affects critical data or functionality and leaves users with no workaround. - Significant catastrophic impact.- A problem that is blocking the ability to work. An immediate fix is needed.

SeveritySeverity is a measure of how ‘bad’ the bug is and how much disruption it causes, without regard to remaining work or the release schedule.“

SEVERITYDESCRIPTION

S1

- Affects critical data or functionality and forces users to employ a workaround.- Impact to the key product qualities.- An immediate fix is needed.

SEVERITYDESCRIPTION

S2

- Affects non-critical data or functionality and forces users to employ a workaround.- Impact to the product qualities that makes the product more usable.- Major restrictions or short-term circumventions are required until a fix is available. A fix is important.

SEVERITYDESCRIPTION

S3

- Affects non-critical data or functionality and does not force users to employ a workaround.- Problem has moderate impact requiring some restrictions. The fix is in an area that is not critical.

SEVERITYDESCRIPTION

S4

- A minor problem, annoyance, or technical issue with minimal impact.- Impact that does not prevent or hinder functionality.- Affects aesthetics, professional look and feel, “quality” or “usability”.

Priority

“

PRIOTIRYDESCRIPTION

P0

- The defect needs to be fixed right now, everything else can wait.- This generally occurs in cases when the entire functionality is blocked

Priority signifies how important or detrimental a defect is. The defect priority status is set by Product Managers. Priority also helps to determine the scheduling of the fix: Higher priority bugs will be fixed and merged first. It is a reflection on how bad the bug is for the system and also for business or marketing requirements.

PRIOTIRYDESCRIPTION

P1

- Needs to be fixed before any other issues.- Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing

PRIOTIRYDESCRIPTION

P2

- Should be fixed as early as possible - A defect with this priority could have functionality issues which are not to expectations

P3

- May be fixed according to the position in the backlog.

PRIOTIRYDESCRIPTION

P4

- No current plan to fix. Fixing can be deferred as a logical part of more important work.

Store incident, avoid forgetting

Step 1: Reporter access to Shark Service Desk - Report Bug

Step

Report BugOutcome

Process

If SharkBA help to create, please note who is the Reporter“

Step 2: Reporter fill content using TemplateStep 3: Reporter attach label Severity and PriorityStep 4: Reporter link to customer Project/Issue or tag the other related Reporter

Reporter

Owner

Receive & First ResponseOutcome

Quick analysit

Step 1: SharkBA: If this already be fixed, link to the old issue, closed and answer to the Reporter on the Reporter channel!

Step 2: SharkBA: Try to Replicate. Re-Evaluate Severity and Priority if SharkBA can replicate.Step 3: SharkBA: Create Issued to Point of Sales Project

Process

Step 4: SharkBA: Add Issue to Jira in specific SprintStep 5: SharkBA: Update brief plan for Reporter on their channel"

Shark BA inform Reporter

Owner

Analyst & Diagnose & First PlanOutcome

Analyst reason, having some workaround

Step 1: If Severity S0, S1 or Priority: P0, P1 then SharkBA show team on daily.Step 2: Shark discuss solution on dailyStep 3: Shark update plan if need by Add to specific SprintStep 4: SharkBA Inform brief plan and solution for Reporter on their channel (tag Reporter)"

Shark DeveloperShark BA inform Reporter

Update about when complete

Step 1: Review remaining list of Incident, sort by PriorityStep 2: Pick maximize 5 and discuss solutionStep 3: Update plan if having change plan by add specific SprintStep 4: SharkBA Inform brief plan and solution for Reporter on their channel"

Process

Owner

Weekly PlanningOutcome

Process

Owner

Shark DeveloperShark BA inform Reporter

Update about complete or not.Share plan or update for customerAvoid duplicate error on another Customer

Step 1: SharkBA Inform result for All channel if Severity S0, S1 or Priority: P0, P1Step 2: SharkBA Inform result for Reporter on their channel if Severity S0, S1 or Priority: P0, P1

Shark DeveloperShark BA inform Reporter

Update about complete or not,share plan or update for customerAvoid duplicate on the future project

ResolveOutcome

Process

Owner

ReleaseOutcome

Check on Slack #noti-release-train

Shark DeveloperShark BA inform Reporter

Process

Owner