Difference between revisions of "User:Afontquerni"

From IGEP - ISEE Wiki

Jump to: navigation, search
(IGEP Bug tracking)
(Reporting Steps)
Line 11: Line 11:
 
=== Step 00: Search for already reported issue ===
 
=== Step 00: Search for already reported issue ===
 
Visit "[http://downloads.isee.biz/mantisbt/view_all_bug_page.php View Issues] webpage and use filters and search box to find it.
 
Visit "[http://downloads.isee.biz/mantisbt/view_all_bug_page.php View Issues] webpage and use filters and search box to find it.
 
  
 
=== Step 01: Report new issue ===
 
=== Step 01: Report new issue ===
Line 44: Line 43:
 
==== Step 01.08: Press 'Submit Report' button ====
 
==== Step 01.08: Press 'Submit Report' button ====
 
Press 'Submit Report' button ends issue reporting.<br>
 
Press 'Submit Report' button ends issue reporting.<br>
After that it will assigned a number which is identificator of issue
+
After that it will assigned a number which is identificator of issue<br>
 +
<br>
 +
See bellow captured screen example:<br>
 +
[[File:01_xx-bugtracking_new_issue.png]]
  
 
== Workflow  ==
 
== Workflow  ==

Revision as of 17:09, 5 July 2012

IGEP Bug tracking

Overview

This article describe IGEP bug tracking system and workflow

Introduction

IGEP Bug tracking system (http://downloads.isee.biz/mantisbt/view.php) is based on MantisBT


Reporting Steps

Step 00: Search for already reported issue

Visit "View Issues webpage and use filters and search box to find it.

Step 01: Report new issue

If you don't already find issue about your question/feature/missing, you could open issue at "Report Issue"

Step 01.01: Choose 'Project'

On right and top it could be selected apropiated project (hardware board, software package, firmware)

Step 01.02: Choose 'Category'

When it is reported some issue, it could be selected these several types:

  • bug: missing or wrong functionality
  • change: change something or adjust configuration
  • feature: add something or new feature
  • remove: delete or remove something or feature
  • request: costumer request or improvement. IGEP commumity will evaluate which changes will need to do.

Step 01.03: Select 'Product Version' (OPTIONAL)

Step 01.04: 'Summary' - Write a complete and short title about issue

Like a subject in e-mail, summary of an issue is a title of your message that will identify them about reason and theme of this issue

Step 01.05: Write detailed 'Description' about issue

Describe any information about issue. First paragraph should be an introduction and resume about that.

Step 01.06: Describe 'Steps To Reproduce' that issue (OPTIONAL)

It will make easy to analize issue if we could reproduce by ourselves

Step 01.07: Attach file with 'Upload file' (OPTIONAL)

Sometimes, an image or a source code patch are the best way to show issue

Step 01.08: Press 'Submit Report' button

Press 'Submit Report' button ends issue reporting.
After that it will assigned a number which is identificator of issue

See bellow captured screen example:
01 xx-bugtracking new issue.png

Workflow

Issues have several states:

  • NEW: First state when issue is created
  • ASSIGNED: Somebody has assigned and that person is responsible for resolving/response issue
  • RESOLVED: Issue has been resolved
  • CLOSED: Issue has been finished (tested OK and archived)

Issues have several participants:

  • manager
  • developer
  • reporter

Workflow or states issue life and actions:

[anybody] NEW (start point) -> [manager] ASSIGNED (responsability) -> [developer] RESOLVED (solution) -> [manager] CLOSED (end point)
          \<--  (needs something) FEEDBACK [developer]<--/


Contribution & Support

Contributions to this project be welcome and you can send your patches to support@iseebcn.com or you can use the igep forum for it.
You can access to IGEP-x-Loader repository using our git at git.igep.es
IGEP IRC Channel: http://webchat.freenode.net/?channels=igep