0
edits
Changes
Created page with '= IGEP Bug tracking = == Overview == This article describe IGEP bug tracking system and workflow == Introduction == IGEP Bug tracking system ([http://downloads.isee.biz/manti…'
= 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 http://downloads.isee.biz/mantisbt/view.php]) is based on [http://www.mantisbt.org/ MantisBT]
== Reporting Steps ==
=== 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.
=== Step 01: Report new issue ===
If you don't already find issue about your question/feature/missing, you could open issue at "[http://downloads.isee.biz/mantisbt/bug_report_page.php 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, clear 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
Estats:
[ANYBODY] new (inici) -> assign (responsabilitat) -> [DEVELOPER] resolve (pendent verificacio) [MANAGER]-> closed (final)
\ <--------- feedback (revisar) <------------ /
== Overview ==
This article describe IGEP bug tracking system and workflow
== Introduction ==
IGEP Bug tracking system ([http://downloads.isee.biz/mantisbt/view.php http://downloads.isee.biz/mantisbt/view.php]) is based on [http://www.mantisbt.org/ MantisBT]
== Reporting Steps ==
=== 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.
=== Step 01: Report new issue ===
If you don't already find issue about your question/feature/missing, you could open issue at "[http://downloads.isee.biz/mantisbt/bug_report_page.php 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, clear 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
Estats:
[ANYBODY] new (inici) -> assign (responsabilitat) -> [DEVELOPER] resolve (pendent verificacio) [MANAGER]-> closed (final)
\ <--------- feedback (revisar) <------------ /