Difference between revisions of "How to report a bug ?"

From DARO
 
(29 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
With this project, we wanted to be able to solve all problems quickly. That's why our bugtracker is available just for you !
 
With this project, we wanted to be able to solve all problems quickly. That's why our bugtracker is available just for you !
  
−
== Créer un ticket ==
+
<div class="center-item">
 +
  '''By following the link below, you will be able to access to the program used to report a bug thanks to all tickets'''
 +
</div>
 +
<div class="center-item">
 +
<html><a href="http://mysticprojectro.com/bug-tracker/index.php">Click here to access to the Bug Tracker</a></html>
 +
</div>
 +
 
 +
== Create an account ==
  
 
<div class="center-item">
 
<div class="center-item">
−
   '''/!\ Before creating a ticket : Check in the list that your report hasn't been already done by someone. /!\'''
+
   '''To access to the bug tracker, you must create an account.'''
 
</div>
 
</div>
 +
:*You can put a '''false''' name, firstname and optional phone, however the e-mail have to be correct and accessable to confirm your registration.
 +
:**An e-mail with a link will be sent in order to verify your account. Do not hesitate to check your junk mail or spam box. If you don't receive the confirmation email, please contact Shin Bi (Discord) for manual validation.
 +
 +
== Create a ticket ==
  
 
As long as you are logged in, click on the green button called '''New Ticket''' located at the top left corner of your screen.
 
As long as you are logged in, click on the green button called '''New Ticket''' located at the top left corner of your screen.
Line 22: Line 33:
 
! Examples
 
! Examples
 
|-
 
|-
−
| Bug
+
! Bug
 
| A dysfunction has been found & an administrator has to proceed to solve the problem.
 
| A dysfunction has been found & an administrator has to proceed to solve the problem.
 
| <ul>
 
| <ul>
Line 29: Line 40:
 
</ul>
 
</ul>
 
|-
 
|-
−
| Suggestion
+
! Suggestion
 
| In your opinion, an upgrade can be done. Administrators can accept or decline the proposal.
 
| In your opinion, an upgrade can be done. Administrators can accept or decline the proposal.
 
| <ul>
 
| <ul>
Line 37: Line 48:
 
|}
 
|}
  
−
===== 2. Assignments =====
+
===== 2. Category & sub-category =====
−
 
 
−
Depending of the ticket, assign it to the corresponding administrator :
 
−
 
 
−
{| class="wikitable weapons-table" style="text-align: center; margin: auto; width: 50%; border-collapse: separate; padding: 0.5em;"
 
−
|-
 
−
! Source
 
−
! Who is concerned ?
 
−
|-
 
−
| Kugans
 
−
| Lutie
 
−
|-
 
−
| Maps
 
−
| Grenat
 
−
|-
 
−
| Website
 
−
| Shin Bi
 
−
|}
 
−
 
 
−
===== 3. Category & sub-category =====
 
  
 
Select the category then the corresponding sub-category of your report.
 
Select the category then the corresponding sub-category of your report.
Line 63: Line 55:
 
::**'''In Game''' → '''[Character]''' → '''Kugan'''.
 
::**'''In Game''' → '''[Character]''' → '''Kugan'''.
  
−
===== 4. Title =====
+
===== 3. Title =====
  
 
Name your ticket with the matter of it.
 
Name your ticket with the matter of it.
Line 69: Line 61:
 
::*For example : Pyromancer Kugan consume way too much SP.
 
::*For example : Pyromancer Kugan consume way too much SP.
  
−
===== 5. Description=====
+
===== 4. Description=====
  
 
Describe the problem. You can formatting your message and import pictures & screenshots. Try to be precise, it will help the comprehension.
 
Describe the problem. You can formatting your message and import pictures & screenshots. Try to be precise, it will help the comprehension.
Line 75: Line 67:
 
Some crucial informations can be mentionned in order to fix a bug :
 
Some crucial informations can be mentionned in order to fix a bug :
  
−
::*Some examples :
+
<ul><li>Examples :</li>
−
<ul>
+
<ul><li><li>Character's class</li></li>
−
::**<li>Character's class</li>
+
<li><li>Equipments / Kugans</li></li>
−
::**<li>Equipments / Kugans</li>
+
<li><li>Location of incident (/where)</li></li>
−
::**<li>Location of incident (/where)</li>
+
</ul></ul>
−
</ul>
+
 
 +
===== 5. Priority =====
  
−
===== 5. Priorité=====
+
This field allows you to assign a priority to your ticket. It will help Administrators to be more efficient and solve all encountered problems in order to offer the best support to players.
  
−
Ce champ permet de placer une priorité sur votre demande. Cela permettra aux admins de traiter d'abord les tickets urgents et/ou de mieux s'organiser.
 
−
Quelques exemples :
 
 
<ul>
 
<ul>
−
<li>Emergency : le comportement fait planter le serveur, le comportement peut être "abusé" si exploité par les joueurs, etc.</li>
+
<li>'''Emergency :''' A bug that keep people unable to play due to crashes. It also concerns bug-abuse possibilties</li>
−
<li>High : le comportement fait planter votre jeu, le bug empêche l'avancement dans le jeu, etc</li>
+
<li>'''High :''' Your own game crash due to something. It also concerns problems affecting in-game progression</li>
−
<li>Medium : le bug est dérangeant</li>
+
<li>'''Medium :''' A troublesome bug. Nonetheless, you still can play and progress in-game.</li>
−
<li>Low : le problème est bénin, le bug est esthétique, le bug peut être contourné par un autre moyen, etc.</li>
+
<li>'''Low :''' A visual issue or some bugs that can be easily ignored or dodge thanks another way. However, the bug exist and must be resolved.</li>
 
</ul>
 
</ul>
  
−
Et pour valider, cliquez sur '''"Submit"'''.
 
  
−
== Les différents états d'un ticket ==
+
At the end of the form, you will have to click on '''Submit''' to create it.
  
 +
== Any news about my ticket ? ==
  
 +
As long as you have submit your ticket, administrators will take care of it as soon as possible ! Don't worry !
 +
Check the state of your ticket in order to know the bug progress.
  
−
{| class="wikitable weapons-table" style="text-align: center; margin: auto; width: 80%; border-collapse: separate; padding: 0.5em;"
+
 
 +
{| class="wikitable weapons-table" style="text-align: center; margin: auto; width: 85%; border-collapse: separate; padding: 0.5em;"
 
|-
 
|-
−
! Ordre
+
!  
−
! Libellé
 
 
! Description
 
! Description
−
! Assigné à
+
! width="15%"| Assigned to
 
|-
 
|-
−
| 1
+
! New
−
| New
+
| <ul><li>The ticket is new and still not in charge of any administrator.</li></ul>
−
| Le ticket vient d'être créé et n'est pas encore associé à un admin
 
 
| -
 
| -
 
|-
 
|-
−
| 2
+
! In progress
−
| In progress
+
| <ul><li>The ticket is currently studied.</li></ul>
−
| Le ticket a été vu par un admin et il est en cours de résolution
 
 
| Admin
 
| Admin
 
|-
 
|-
−
| 3
+
! Waiting informations
−
| Waiting informations
+
| <ul><li>Some informations are missing in order to solve or to understand the bug, you must provide more informations.</li></ul>
−
| Le ticket a été vu par un admin mais il manque des éléments pour la résolution du problème
+
| Player
−
| Beta testeur
 
 
|-
 
|-
−
| 4
+
! Resolved
−
| Resolved
+
| <ul><li>The bug has been resolved by an administrator.</li></ul>
−
| Le ticket a été résolu par un admin
 
 
| Admin
 
| Admin
 
|-
 
|-
−
| 5
+
! Rejected
−
| Rejected
+
| <ul><li>The ticket has not been approved and will not be handled. This state is used if the ticket is already created or if the bug can't be reproduced.</li></ul>
−
| Le ticket a été rejeté par un admin (doublon de tickets, bug non constaté, etc)
 
 
| Admin
 
| Admin
 
|-
 
|-
 
|}
 
|}

Latest revision as of 10:22, 6 January 2022

Introduction

With this project, we wanted to be able to solve all problems quickly. That's why our bugtracker is available just for you ! 

  By following the link below, you will be able to access to the program used to report a bug thanks to all tickets

Click here to access to the Bug Tracker

Create an account

  To access to the bug tracker, you must create an account.
  • You can put a false name, firstname and optional phone, however the e-mail have to be correct and accessable to confirm your registration.
    • An e-mail with a link will be sent in order to verify your account. Do not hesitate to check your junk mail or spam box. If you don't receive the confirmation email, please contact Shin Bi (Discord) for manual validation.

Create a ticket

As long as you are logged in, click on the green button called New Ticket located at the top left corner of your screen. You will have to fulfil several field of the form :

1. Tickets' Types

Select Bug or Suggestion.

Description Examples
Bug A dysfunction has been found & an administrator has to proceed to solve the problem.
  • The game is laggy or it crashes
  • In game, the effect of a feature is different from expected, based on the Wiki informations.
Suggestion In your opinion, an upgrade can be done. Administrators can accept or decline the proposal.
  • Two NPCs are too close from each other. These one can't be targetted easily.
2. Category & sub-category

Select the category then the corresponding sub-category of your report.

  • For example, if you found a problem with a Kugan, choose :
    • In Game → [Character] → Kugan.
3. Title

Name your ticket with the matter of it.

  • For example : Pyromancer Kugan consume way too much SP.
4. Description

Describe the problem. You can formatting your message and import pictures & screenshots. Try to be precise, it will help the comprehension.

Some crucial informations can be mentionned in order to fix a bug :

  • Examples :
    • Character's class
    • Equipments / Kugans
    • Location of incident (/where)
5. Priority

This field allows you to assign a priority to your ticket. It will help Administrators to be more efficient and solve all encountered problems in order to offer the best support to players.

  • Emergency : A bug that keep people unable to play due to crashes. It also concerns bug-abuse possibilties
  • High : Your own game crash due to something. It also concerns problems affecting in-game progression
  • Medium : A troublesome bug. Nonetheless, you still can play and progress in-game.
  • Low : A visual issue or some bugs that can be easily ignored or dodge thanks another way. However, the bug exist and must be resolved.


At the end of the form, you will have to click on Submit to create it.

Any news about my ticket ?

As long as you have submit your ticket, administrators will take care of it as soon as possible ! Don't worry ! Check the state of your ticket in order to know the bug progress.


Description Assigned to
New
  • The ticket is new and still not in charge of any administrator.
 -
In progress
  • The ticket is currently studied.
 Admin
Waiting informations
  • Some informations are missing in order to solve or to understand the bug, you must provide more informations.
 Player
Resolved
  • The bug has been resolved by an administrator.
 Admin
Rejected
  • The ticket has not been approved and will not be handled. This state is used if the ticket is already created or if the bug can't be reproduced.
 Admin
Retrieved from "http://mysticprojectro.com/wiki/index.php?title=How_to_report_a_bug_%3F&oldid=10095"