FIBARO BUG TRACKER USER GUIDE

Transcription

1 FIBARO BUG TRACKER USER GUIDE Fibaro Bug Tracker is software application that is designed to help quality assurance and Fibaro System programmers keep track of reported software bugs and issues in their work. It may be regarded as a type of issue tracking system. 1) Main menu elements Main - link to main page My View - preview of all My reported bugs and my monitored bugs View Issues - lpreview of all reported bugs with advanced filtering possibilities Report Issue - link to reporting sheet Change Log - information about recent changes and software updates Roadmap - informations about future projects and releases My Account - personal settings and preferences (include language preferences) Logout Projects: Projects are separate test subjects. If there is more then 1 projects assigned to users there is possibility to switch between them and reporting bugs to each folder separately. 2) My View My View is personal view for reported bugs. Unassigned - bugs that will be considered by developer team Resolved - known and solved issues Reported by Me - my reported bugs Recently Modified - recently modified bugs Monitored by me - bugs that was added to my monitor list All reported bugs are classified by following groups (marked by colors):

2 new - new and not considered reports that will feedback - new issues that request feedback informations acknowledged - considered issues that will request further action confirmed - considered issues that was confirmed assigned - confirmed bugs that was assigned to specyfic person/department resolved - confirmed bugs that was resolved closed - resolved bugs that was finally closed 3) View issues This section is used for viewing reported and known bugs. First upper part is advanced filter used for specifying reported bugs. Second lower part is list of reported bugs. All bugs are marked by the same as in My View section specyfic colors. All reported bugs are classified by following groups (marked by colors): new - new and not considered reports that will feedback - new issues that request feedback informations acknowledged - considered issues that will request further action confirmed - considered issues that was confirmed assigned - confirmed bugs that was assigned to specyfic person/department resolved - confirmed bugs that was resolved closed - resolved bugs that was finally closed 4) Report issue Report issue is the section where you can report your bug. This section is based on few elements. First section is basic information about:

3 Category Reproducibility Severity Software profile Next element are description fields. Please provide as much information as possible. You can also attach screenshot or any file to your report. Last step is submiting the report. In this element you can define if you will create public or private report. Public reports are visible for all users while private reports are visible only for assigned users. 5) My Account My account section is used for personal settings, and user status information.

4 There is also possibility to change language settings. It can be done in Preference tab. Example I Searching for earlier reports It is recommended to search for earlier reports before creating the new one. To use advanced filter please click: To view specyfic issue information please click at ID number:

5 Preview of the report looks as follows: If user wants to follow specyfic issue there is option MONITOR. Monitored threds will be available in My View menu. There is also possibility to add comments to existing reports: Issue modification are located in lewer part of the section:

6 Example II New issue reporting If bug found by the user was not earlier reported there is possibility to create the new report. New report should be always presented in appropriate project. First of all please fill Category, Reproducibility, Severity and priority fields. Next please create descritpion of the issue. Please provide description that is detailed as much as possible. Is it also helpfull to add file (for example with issue screenshot):

7 In next step user can determine whether his report should be visible to all users (public) or only for development team (private). The last step is submitting the report.