jira - submitting new bug

7/30/2019 Jira - Submitting New Bug

1/24

How to write a bug

First step is to find it.


2/24

After you find the bug

Dont be so happy, you will have to checkit.

First be sure that the steps you find for thereproduction of the bug are correctly.

Second be sure that is not a DUPLICATE.

Third check if the bug occurs somewhereelse or how is affecting the game.


3/24

You have a Bug


4/24

Open the Jira Database

http://mdc-tomcat-jira15.ubisoft.org/jira/secure/Dashboard.jspa

(for training only).
http://mdc-tomcat-jira15.ubisoft.org/jira/secure/Dashboard.jspahttp://mdc-tomcat-jira15.ubisoft.org/jira/secure/Dashboard.jspahttp://mdc-tomcat-jira15.ubisoft.org/jira/secure/Dashboard.jspahttp://mdc-tomcat-jira15.ubisoft.org/jira/secure/Dashboard.jspahttp://mdc-tomcat-jira15.ubisoft.org/jira/secure/Dashboard.jspahttp://mdc-tomcat-jira15.ubisoft.org/jira/secure/Dashboard.jspahttp://mdc-tomcat-jira15.ubisoft.org/jira/secure/Dashboard.jspa


5/24

Create new issue


6/24

Select Training as project and Bug Qc as

Issue Type than click NEXT


7/24

Summary

This is usually a sentence as short as

possible but most descriptive as

possible. The nomenclature followed

is; [The map where the bug can be

found]A sentence describing thebug (and the platform if specific to a

platform).

For example: [Ep05 Beach05] AI

Check Error when speaking to

Locked


8/24

Description

This section is used to further

describe a bug in details. As much

information should be provided

here.


9/24

Expected BehaviorThe expected behaviour of a bug should

be described here. It is basically what

should occur in the game.


10/24

Steps to Reproduce

Used to list the steps followed in

order to reproduce the bug. List

them using: 1-, 2-, 3-, etc.

Also there is an template that we

use for writing the bug:

Ex: For a graphic bug that occurson a specific place on the map.

When the user:

1. Enters the map.

2. Goes to the location shown inpicture.

3. Look at the tree.

The following occurs:

1. The texture is flickering.

Note:

The lines that are written with

red are very important and

must be written at all the bugs


11/24

Platform / Module Specify on which platform thebug occurs on.


12/24

Affects Version/s

Specify the version where the bug

was found. At no point in time

should this field be modified. If

the bug was checked on a laterversion and still occurs, the field

Last Observed Product is used

to specify that when editing a bug.

(Ex. Lost_202)


13/24

Location Specify the location where the

bug can be found.


14/24

Sub LocationSpecify the sub location of where

the bug can be found


15/24

Severity

Give a severity to the bugdepending on its gravity.

IMPORTANT : Be sure that you

chose correct severity.


16/24

Milestone The milestones are the dead-linesestablished for different stages of

the game.

Ex: alpha, beta, master, etc.


17/24

Walkthrough Break A field that allows the tester to seta bigger severity on a bug. All

walkthrough breakers are S1 by

default.


18/24

WorkaroundSpecify, using the drop-down list,

if the bug can be avoided.

ATTENTION!!! All the steps

from the steps to reproduce must

be respected. Once you eliminate

or put one step the workaround is

no longer available.


19/24

Component/s Select the component that bestdescribes the type of bug.

On training you will choose

Training Romania.


20/24

AssigneeUnless otherwise specified, the

Components section will

automatically send the bug.Therefore, this field need not to be

filled unless an Assignee has been

identified.

For the training you will choose

Ionut Socolovici.


21/24

Scope Select the scope(s) that bestdescribe the type of bug. Restrict

from using multiple scopes if not

needed.

ATTENTION: The scope you

chose is very important because if

you dont choose the good

scope(s) the bug can be assigned

to a wrong developer.


22/24

Attachment Select the picture files to beattached. Video files are also

accepted but only used when a

bug cannot be identified from a

picture. The maximum file upload

size if 10 MB, and up to 4

attachments can be posted. If a(n)

attachment needs to be

deleted/replaced, please see yourLead.

ATTENTION: The pictures and

movies that you attached must be

clear and precise !!!

Also must be renamed like in the

following example:Ionut Socolovici that works at

Lost on PS3.

Isoc_Lost_Ps3_001.jpg(avi)


23/24

Repro RateTechnical reproducibility usually

should be 100% but if you cant

find the steps that makes the bug

100% repro you will declare it at a

small repro with the steps that you

have.

Also the reproducibility is not

necessary based on percentage

some leads might ask you to

wrote how many tries on howmany times occurs.

Ex: a bug that appears 7 times on

15 tries will have a 7 of 15 repro.


24/24

Now you have the basics by Soco

jira - submitting new bug

Documents