Skip to content

Commit

Permalink
deploy: 4b61b8a
Browse files Browse the repository at this point in the history
  • Loading branch information
@kpodemski
kpodemski committed Feb 16, 2024
1 parent 604ea4c commit d3bb5fc
Show file tree
Hide file tree
Showing 4 changed files with 24 additions and 24 deletions.
38 changes: 19 additions & 19 deletions get-involved/report-issues/how-issues-are-sorted/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@
<head>
<meta charset="utf-8">
<title>How issues are sorted | PrestaShop Project - Open Source e-Commerce platform</title>
<meta name="description" content="How issues are sorted What happens to the issue you have reported PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity, and how they should be applied through labels on GitHub issues.
Please note that severity is to be distinguished from priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development."/>
<meta name="description" content="How issues are sorted What happens to the issue you have reported The PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity and how they should be applied through labels on GitHub issues.
Please note that the severity is to be distinguished from the priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development."/>

<link rel="canonical" href="https://www.prestashop-project.org/get-involved/report-issues/how-issues-are-sorted/" itemprop="url" />

Expand All @@ -27,15 +27,15 @@

<!-- Open Graph image and Twitter Card metadata -->
<meta name="twitter:title" content="How issues are sorted"/>
<meta name="twitter:description" content="How issues are sorted What happens to the issue you have reported PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity, and how they should be applied through labels on GitHub issues.
Please note that severity is to be distinguished from priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development."/>
<meta name="twitter:description" content="How issues are sorted What happens to the issue you have reported The PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity and how they should be applied through labels on GitHub issues.
Please note that the severity is to be distinguished from the priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development."/>
<meta property="og:title" content="How issues are sorted" />
<meta property="og:description" content="How issues are sorted What happens to the issue you have reported PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity, and how they should be applied through labels on GitHub issues.
Please note that severity is to be distinguished from priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development." />
<meta property="og:description" content="How issues are sorted What happens to the issue you have reported The PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity and how they should be applied through labels on GitHub issues.
Please note that the severity is to be distinguished from the priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://www.prestashop-project.org/get-involved/report-issues/how-issues-are-sorted/" /><meta property="article:section" content="get-involved" />

<meta property="article:modified_time" content="2022-11-30T17:10:41+01:00" />
<meta property="article:modified_time" content="2024-02-16T10:50:03+00:00" />



Expand Down Expand Up @@ -302,8 +302,8 @@
<div class="col-xl ml-auto">
<div class="content"><h1 id="how-issues-are-sorted">How issues are sorted</h1>
<h2 id="what-happens-to-the-issue-you-have-reported">What happens to the issue you have reported</h2>
<p>PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues' severity, and how they should be applied through labels on GitHub issues.</p>
<p>Please note that severity is to be distinguished from priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development. It is usually defined by the QA team. As for the priority, it is used to organize all the tasks (bugs, improvements, features, technical tasks) that have to be done in order to meet the project&rsquo;s deadlines.</p>
<p>The PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues' severity and how they should be applied through labels on GitHub issues.</p>
<p>Please note that the severity is to be distinguished from the priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development. It is usually defined by the QA team. As for the priority, it is used to organize all the tasks (bugs, improvements, features, technical tasks) that have to be done in order to meet the project&rsquo;s deadlines.</p>
<h2 id="issue-severity-criteria">Issue Severity Criteria</h2>
<p>When a new issue is created, the first step is to understand what the problem is and then reproduce it. Once that work is done, the second step is to define the severity of that bug.</p>
<p>Four severity levels are used: Critical, Major, Minor and Trivial.</p>
Expand All @@ -316,7 +316,7 @@ <h3 id="critical">Critical</h3>
</ul>
<p>Examples:</p>
<ul>
<li>Difficulty accessing the front office or back office (significant slowdown, error during installation or update, fatal error)</li>
<li>Difficulty to access the Front Office or Back Office (significant slowdown, error during installation or update, fatal error)</li>
<li>Difficulty to globally manage categories, products or customers</li>
<li>Difficulty to globally place and manage orders</li>
</ul>
Expand All @@ -326,14 +326,14 @@ <h3 id="major">Major</h3>
<p>A major issue affects a large percentage of users (&gt; 30%) and matches at least one of the following:</p>
<ul>
<li>It impacts law compliance</li>
<li>It has a strong impact on the usability of the front office / back office or blocks another project</li>
<li>It is an important problem but not necessarily blocking the main activity of the seller</li>
<li>It has a strong impact on the usability of the Front Office / Back Office or blocks another project</li>
<li>It is an important problem but doesn&rsquo;t necessarily block the main activity of the seller</li>
</ul>
<p>Examples:</p>
<ul>
<li>Being unable to add, configure or delete a theme or a module</li>
<li>Difficulty in operating a module properly</li>
<li>Impacts the price the customer pays</li>
<li>Inability to add, configure or delete a theme or a module</li>
<li>Difficulty to operate a module properly</li>
<li>Impact on the price the customer pays</li>
</ul>
<h3 id="minor">Minor</h3>
<p>The bug affects minor functionality or non-critical data and there is a reasonable workaround, even if it can be annoying when using your shop.</p>
Expand All @@ -356,14 +356,14 @@ <h3 id="trivial">Trivial</h3>
</ul>
<h2 id="issue-prioritization">Issue Prioritization</h2>
<p>Assessing severity helps to prioritize issues, but it is not the only criterion at stake. Given two equally severe issues, how to choose one over the other?</p>
<p>Prioritization is done by representatives of the Development team, the Product Management team, and the Quality Assurance team.</p>
<p>Together, during regular meetings, they look at the new confirmed issues and they sort them.</p>
<p>In order to make sure that a given bug does not damage PrestaShop&rsquo;s image nor it affects the confidence merchants can have in PrestaShop, they take special care and strive to make every version of PrestaShop better than the one before. Since no one wants to introduce new bugs while fixing other bugs, regressions (new bugs created accidentally when fixing or improving an existing feature) are usually prioritized higher than older bugs. By doing this, the overall software stability is ever increasing.</p>
<p>Prioritization is done by representatives of the Development team, the Product Management team and the Quality Assurance team.</p>
<p>Together, during regular meetings, they look at the new confirmed issues and sort them.</p>
<p>In order to make sure that a given bug does not damage PrestaShop&rsquo;s image nor it affects the confidence merchants can have in PrestaShop, they take special care and strive to make every version of PrestaShop better than the previous one. Since no one wants to introduce new bugs while fixing other bugs, regressions (new bugs created accidentally when fixing or improving an existing feature) are usually prioritized higher than older bugs. By doing this, the overall software stability is ever increasing.</p>
<p>Then the issue&rsquo;s technical complexity is also studied: that is, whether the bug is easy or complex to fix.</p>
<p>Sometimes a smaller bug will be prioritized over a bigger one. This is because a complex bug may require big technical changes which are not suitable until a later version. This may be because it would require applying backward-incompatible changes (which are bad for module developers), or because it can be better addressed as a part of a larger project – there is no use fixing a bug if the whole feature is due to be revamped in the near future.
Also sometimes some bugs will be prioritized just because of the “opportunity cost” of fixing them together, as it is usually easier to fix several bugs within the same component. For instance, during the migration of a BO page to Symfony, the bugs of this page are prioritized higher in order to fix them all at once.</p>
<p>The last criterion used is the business impact, of course.</p>
<p>In the end, handling bugs requires two points of view: micro and macro. Severity analyzes the issue on its own, while Priority analyzes the issue in the context of the whole project.</p>
<p>In the end, handling bugs requires two points of view: micro and macro. Severity analyzes the issue on its own, while Priority analyzes the issue within the context of the whole project.</p>
<hr>
<p><em>(This article was originally published on our blog: <a href="https://build.prestashop-project.org/news/severity-classification/">Introducing A New Bug Severity Classification</a>)</em></p>
</div>
Expand Down
4 changes: 2 additions & 2 deletions get-involved/report-issues/index.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/get-involved/report-issues/how-issues-are-sorted/</guid>
<description>How issues are sorted What happens to the issue you have reported PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity, and how they should be applied through labels on GitHub issues.
Please note that severity is to be distinguished from priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development.</description>
<description>How issues are sorted What happens to the issue you have reported The PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity and how they should be applied through labels on GitHub issues.
Please note that the severity is to be distinguished from the priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development.</description>
</item>

</channel>
Expand Down
4 changes: 2 additions & 2 deletions index.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -202,8 +202,8 @@ We require from maintainers to take the necessary steps to make sure this accoun
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

<guid>https://www.prestashop-project.org/get-involved/report-issues/how-issues-are-sorted/</guid>
<description>How issues are sorted What happens to the issue you have reported PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity, and how they should be applied through labels on GitHub issues.
Please note that severity is to be distinguished from priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development.</description>
<description>How issues are sorted What happens to the issue you have reported The PrestaShop Quality Assurance team (aka QA) uses a transparent definition for the criteria used to qualify issues&#39; severity and how they should be applied through labels on GitHub issues.
Please note that the severity is to be distinguished from the priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development.</description>
</item>

<item>
Expand Down
2 changes: 1 addition & 1 deletion sitemap.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@
<lastmod>2023-04-24T17:02:58+02:00</lastmod>
</url><url>
<loc>https://www.prestashop-project.org/get-involved/report-issues/how-issues-are-sorted/</loc>
<lastmod>2022-11-30T17:10:41+01:00</lastmod>
<lastmod>2024-02-16T10:50:03+00:00</lastmod>
</url><url>
<loc>https://www.prestashop-project.org/project-organization/quality-council/processes/contribute-ui-tests/</loc>
<lastmod>2024-01-22T10:05:02+01:00</lastmod>
Expand Down

0 comments on commit d3bb5fc

Please sign in to comment.