Mantis

From UG

(Difference between revisions)

Jump to: navigation, search

Current revision as of 23:19, 24 May 2010

[edit] Intro

We use Mantis software as a main CT2 Tasks and Bugs Management System.

CT2 Mantis home: http://mantis.jaguarfreight.com/mantis/main_page.php

For any job related to CT2 there is a task in mantis.

Every task is always assigned to someone at any moment in time.

Same task could "travel" from one person to another. For example it could be assigned to developer and then later to QA.

Task would often go through development phases during its lifetime. Each such development phase has its own "folder" called "Project" in Mantis. For example, task to create new component would be posted originally into "Specs" mantis folder and once specs are complete moved into "Dev(elopment)" mantis folder. After task is ready for QA it would be moved to "QA" mantis folder and so on.

For each job title (QA or developer or...) there is a specific CT2 workflow and therefore specific mantis worflow. At the same time there is a lot in common. Some use cases are same for everyone.

[edit] Major Use Case. How to see all your tasks

Log into Mantis.
Click on "View Issues" (main menu at the top)
If Filters panel is not open then open it by clicking on "+" (top left near "Search")
Click on "Assigned To:" filter
Select your name
Click on "Apply Filter"
Click on "Status" column to see sorted by status

System will display ALL your tasks. Example:

[edit] Project field

[edit] Status

Current list:

new
feedback
statusX (on hold)
accepted
started
completed
closed

[edit] Other Task Fields

[edit] How to sort

[edit] How to work with filters

[edit] How to assign task to someone

[edit] How to move task to another phase

[edit] Creating specific tasks for each component

Sys Analyst creates tasks for each component and links as child to parent record so it is easy to see any time what tasks are there for each component and in what state.

Main task would be "Implement ver x.xx". But some of these tasks are bugs, tweaks, etc. For example under parent component 0001015: [Client.LogInPanel] we see:

parent of 	0001016	started	andrei 	4.QAbasic 	[Client.LogInPanel] Implement ver1.0  
parent of 	0001017	new	slava 	00.Graphics 	[Client.LogInPanel] Create Look and Feel for ver# 1.0  
parent of 	0001024	new	dima 	3b.Dev 	        [Client.LogInPanel] BUG: Login from another application hyperlink (MS Exel - hyperlink - Client)

Tasks are classified into:

changes (new features, new versions of existing features/components, tweaks/changes)
bugs

[edit] Decomposing Super Component into Components and Tasks

At some point it will be clear how to split specific super component (and its development) into a number of large subcomponents.

At this point Sys Analyst creates "mantis parent records" for each super component under Mantis project=[SuperCompName]. For example under Mantis Project=>>(Client) for Client Application you will see:

595	[Client.*Misc] =================== Client			
924	[Client.CTdetails]			
919	[Client.HomePage]			
921	[Client.ListAll]			
1015	[Client.LogInPanel]			
685	[Client.LookAndFeel]			
939	[Client.MAWBtracking]			
922	[Client.MyProfile]			
591	[Client.Reports]			
920	[Client.WatchList]			
925	[Client.WhereIs]

[edit] Mantis fields

[edit] Project planning fields

[edit] emh

emh = estimated man hours (to handle the task)

This is set before task is started. And should not be updated because the purpose of this field is to capture original estimate.

[edit] Risk

Risk - degree to which #emh number is probable.

Tasks that are easy to estimate have Risk = 1low (X1)
Tasks that are hard to estimate have Risk = 2low (X2). This means that if emh is set to say 3 hours then task could take as long as 2 X 3 = 6 hours

This is set before task is started. And should not be updated because the purpose of this field is to capture original estimate.

[edit] amh

amh - accumulated man hours - number of hours spent on this task so far. Updated periodically.

amh = 0 before task is started.

rmh will exceed emh in case emh was incorrect or if Risk > 1

[edit] rmh

rmh - remaining man hours - estimated number of hours required to complete this task. Updated periodically.

rmh = emh before tasks is started.

[edit] due

due - estimated date when task will be completed

[edit] Design fields

Below fields are equivalents of some general fields for Design work.

[edit] Requirements fields

Below fields are equivalents of some general fields for Requirements work.

[edit] Rq.Risk

see #Risk

[edit] Rq.emh

see #emh

[edit] Rq.amh

see #amh

[edit] Rq.rmh

see #rmh

[edit] Rq.due

see #due

@@ Line 89: / Line 89: @@
 == Mantis fields ==
-=== Man hours and risk reporting ===
+=== Project planning fields ===
 ==== emh ====
@@ Line 108: / Line 108: @@
 amh = 0 before task is started.
+rmh will exceed emh in case emh was incorrect or if Risk > 1
 ==== rmh ====
 rmh - remaining man hours - estimated number of hours required to complete this task. Updated periodically.
+rmh = emh before tasks is started.
+==== due ====
+due - estimated date when task will be completed
 === Design fields ===
@@ Line 127: / Line 135: @@
 ==== Dz.rmh ====
 see [[#rmh]]
+==== Dz.due ====
+see [[#due]]
+=== Requirements fields ===
+Below fields are equivalents of some general fields for Requirements work.
+==== Rq.Risk ====
+see [[#Risk]]
+==== Rq.emh ====
+see [[#emh]]
+==== Rq.amh ====
+see [[#amh]]
+==== Rq.rmh ====
+see [[#rmh]]
+==== Rq.due ====
+see [[#due]]