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

From DARO
 
(14 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 !
  
−
== Create a 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 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: 80%; border-collapse: separate; padding: 0.5em;"
 
−
|-
 
−
! Source
 
−
! Who is concerned ?
 
−
|-
 
−
| Mob skills/Classes, Mob elite, WoE Domi, Instance 1 (citadel), Zodiac Effect, Mercenary Quests, Spawns Mobs, Left-Handed Weapon, Custom/Modif Status, Gameplay modifs
 
−
| Lutie
 
−
|-
 
−
| Babel, Achievements, Battleground, Summoner, Qpet, Sadrith, Elemental Dungeons, Temples, Instance 2/3, Nightmare Dungeons, Maps bugs/modifs, Quick access, Peco system, Stylist, WoE Origin, Mount, Party System/Skills, Hat Costumes, VIP System, Reborn, Mastery (Lv 100+), Automated Events, Casino, Enchant/Quality System, Weapon Lv 5, Introduction
 
−
| Grenat
 
−
|-
 
−
| Items renewal, Mob custom, Kugan Effects, Skills modifications, Card remover, Gems, Invasions, RP Quests
 
−
| Lutie & 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 67: 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 73: 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 85: Line 73:
 
</ul></ul>
 
</ul></ul>
  
−
===== 6. Priority =====
+
===== 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.
 
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.
Line 99: Line 87:
 
At the end of the form, you will have to click on '''Submit''' to create it.
 
At the end of the form, you will have to click on '''Submit''' to create it.
  
−
== Any news about my previous ticket ? ==
+
== 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 !
 
As long as you have submit your ticket, administrators will take care of it as soon as possible ! Don't worry !
Line 121: Line 109:
 
! 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>
 
| <ul><li>Some informations are missing in order to solve or to understand the bug, you must provide more informations.</li></ul>
−
| Beta Tester
+
| Player
 
|-
 
|-
 
! Resolved
 
! Resolved

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"