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

From DARO
Line 97: Line 97:
 
== Any news about my previous ticket ? ==
 
== Any news about my previous ticket ? ==
  
As long as you have submit your ticket, administrators will take care of it as soon as possible ! Don't worry
+
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;"
 +
|-
 +
! Ordre
 +
! Libellé
 +
! Description
 +
! Assigné à
 +
|-
 +
| 1
 +
| New
 +
| Le ticket vient d'être créé et n'est pas encore associé à un admin
 +
| -
 +
|-
 +
| 2
 +
| In progress
 +
| Le ticket a été vu par un admin et il est en cours de résolution
 +
| Admin
 +
|-
 +
| 3
 +
| Waiting informations
 +
| Le ticket a été vu par un admin mais il manque des éléments pour la résolution du problème
 +
| Beta testeur
 +
|-
 +
| 4
 +
| Resolved
 +
| Le ticket a été résolu par un admin
 +
| Admin
 +
|-
 +
| 5
 +
| Rejected
 +
| Le ticket a été rejeté par un admin (doublon de tickets, bug non constaté, etc)
 +
| Admin
 +
|-
 +
|}

Revision as of 15:55, 29 March 2021

Introduction

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

Create a ticket

  /!\ Before creating a ticket : Check in the list that your report hasn't been already done by someone. /!\

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. Assignments

Depending of the ticket, assign it to the corresponding administrator :

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.

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

Name your ticket with the matter of it.

  • For example : Pyromancer Kugan consume way too much SP.
5. 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)
6. 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 previous 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.


Ordre Libellé Description Assigné à
1 New Le ticket vient d'être créé et n'est pas encore associé à un admin -
2 In progress Le ticket a été vu par un admin et il est en cours de résolution Admin
3 Waiting informations Le ticket a été vu par un admin mais il manque des éléments pour la résolution du problème Beta testeur
4 Resolved Le ticket a été résolu par un admin Admin
5 Rejected Le ticket a été rejeté par un admin (doublon de tickets, bug non constaté, etc) Admin