Bug Triage

Here we document the meaning of the priority levels assigned to reported bugs.

Where the bugs are

• JIRA - iDempiere's Issue Tracker

Select 1 ticket from this list : https://idempiere.atlassian.net/issues/?filter=13313

Explanation of Bug Triage Process

Bug Triage is the process of reviewing a reported bug.

1. Try to Reproduce: You try to reproduce the bug on the latest release repository.
   

   For example you can try to reproduce the bug on the test site https://test.idempiere.org/webui/
   

   As a result of your trial to reproduce one of these three things can happen:

   1. Bug is unclear:

      You can find that redaction of the bug is not clear enough to allow research of the problem, in this case it's recommended that you:

      1. Resolve the ticket assigning Resolution to Incomplete
      2. Add a comment asking for better explanation and steps to reproduce

         Note that the user can reopen the ticket (and must be encouraged too) if he provides more information or ways to reproduce the issue.

   2. Bug cannot be reproduced:

      When you find the bug is clearly explained but you cannot reproduce it in current release repository then it's recommended that you:

      1. Resolve the ticket assigning Resolution to Cannot Reproduce
      2. Add a comment asking for better explanation and steps to reproduce
   3. Bug is reproducible in release repository:

      You find the bug is valid, so it's recommended that you:

      1. Leave status in Open
      2. Assign Components according to the list of Components provided
      3. Assign Priority according to the table described below
      4. Add a comment like "reproduced by _name_of_triager_". It's also recommended to add steps to reproduce when the tracker doesn't have them.

         Please note that assigning correct priority and group are the MOST IMPORTANT steps of this process. With correctly triaged bugs we can plan better the stabilization of releases.

Explanatory Video about Triage Day Mechanism

https://www.youtube.com/watch?v=sY9FhwKaHrA

Helping with Triage

1. You can use our Triage mattermost channel to communicate your Triage efforts
2. Anyone can help. It is a matter of looking at bug reports, trying to reproduce in the daily build, then setting the priority of the bug.
3. Sign up to review a small section of bug reports, at the latest link underneath the heading Volunteering below.
4. Get the latest code/db.
   1. or use the ready-to-run zkwebui client at test.idempiere.org
      1. NOTE: just for the triage day we prepared 10 additional test servers in the addresses triage0, triage1, triage2, triage3, triage4, triage5, triage6, triage7, triage8, triage9

1. 1. or download the daily iDempiere installer from downloads
   2. or download and build the sources yourself, and apply all the latest migration scripts.
2. If you can reproduce the bug in the latest build, set the priorities as noted below.
3. If there is not enough information to reproduce, then you can ask for more details.
4. If you can not reproduce the error, then close the bug, and say 'Works in latest version' ;)

Priority Levels

If you are filling out a report, you can assign the priority according to the following guidelines:

• Blocker - Blocks development and/or testing work, production could not run.
• Critical - Crashes, loss of data, severe memory leak.
• Major - Major loss of function.
• Minor - Minor loss of function, or other problem where easy workaround is present.
• Trivial - Cosmetic problem like misspellings or misaligned text.