File:Prioritizing Bugs Flowchart.jpg

    From The Document Foundation Wiki

    Original file(1,344 × 2,496 pixels, file size: 295 KB, MIME type: image/jpeg)

    Summary

    This flowchart shows an example of how one could triage bug priorities. It is not meant as a strict guideline, only an example that some might find useful. If there are suggestions or issues with it please email me at jmadero - dev at gmail dot com (no spaces). Thanks all.

    Source

    This file is an export of the ODG file File:Prioritizing_Bugs_FlowChart.odg.

    Accessible description

    What follows is the flowchart described as plain text, based on the original ODG file in its 2017-10-27 version

    Bug Priority Triage Flowchart Suggestion(s)

    DEFAULT - Read bottom for more information

    Does bug cause crash, loss of data, inability to install, broken core functions (ex. inability to save or print any document)?

    Yes

    Does this bug happen very frequently on clean install/install attempt?

    Yes

    Email QA & Devs.

    • Priority: Highest
    • Severity: Critical
    No

    Does bug involve major component affecting most users?

    Yes
    • Priority: Highest
    • Severity: Critical
    No

    Does bug affect a component that affects many users?

    = Yes =
    • Priority: High
    • Severity: Critical
    = No =
    • Priority: Medium
    • Severity: Critical

    No

    Does bug involve a serious glitch, such as tedious slowness, inability to open particular documents, install some extensions, print to certain printers?

    Yes
    • Priority: High
    • Severity: Major
    No

    Does bug prevent users from making professional quality work, including exchanging files with other office suites?

    Yes
    • Priority: Medium
    • Severity: Normal
    No

    Does bug make it substantially harder to make high quality work or require users to not use some features?

    = Yes =
    • Priority: Medium
    • Severity: Minor
    = No =

    Does bug not affect ability to make high quality work but instead only suggestions to make current features better? Ex: label names & object placement

    == Yes ==
    • Priority: Low
    • Severity: Trivial
    == No ==

    Bug is not a bug, instead it's a wishlist item for a NEW feature OR a SUBSTANTIAL change on a current feature.

    • Priority: Medium
    • Severity: Enhancement

    Defaults

    Default priorities are just to match to the severity of the bug but can/should be changed if appropriate. Some questions that can be asked while bug triaging to determine if raising/lowering priority is appropriate:

    1. How many people will benefit from this bug getting fixed (most, many, few, almost none)
    2. How easy is the fix for this bug (really easy → really hard)
    3. How much of a time saver would fixing the bug cause for end user.
    4. Is there currently a workaround? If so, how hard is the workaround?
    5. Does the bug reflect poorly on LibreOffice to the community (example might be a simple typo that should be fixed)

    Regressions

    Special attention should be made to prioritizing regressions. Usually a regression calls for increased priority unless there is a specific reason not to raise it, in which case a comment in the bug is probably a good idea.

    Licensing

    CC some rights reserved.svg
    Heckert GNU white.svg
    Mozilla logo.svg

    This work is licensed under three licenses, to be used alternatively or in combination depending on the user's needs:

    File history

    Click on a date/time to view the file as it appeared at that time.

    Date/TimeDimensionsUserComment
    current16:00, 27 October 20171,344 × 2,496 (295 KB)Beluga (talk | contribs)Major layout cleanup
    13:41, 7 December 20161,344 × 2,496 (280 KB)Cornouws (talk | contribs)included few words on taking into account exchanging files with other office-suites.
    23:27, 4 December 20151,344 × 2,496 (285 KB)Qubit (talk | contribs)Update image to reflect deprecation of 'blocker', use of name 'enhancement', and relative position of Importance fields (Priority, Severity) in the Bugzilla web interface.
    20:31, 19 June 20121,008 × 1,872 (481 KB)Jmadero (talk | contribs)This flowchart shows an example of how one could triage bug priorities. It is not meant as a strict guideline, only an example that some might find useful. If there are suggestions or issues with it please email me at jmadero - dev at gmail dot com (no sp

    The following 59 pages use this file: