Bugtracker Help Guide

FluffyLogic uses the Mantis Bugtracker system to add with support of project development. It's a great tool for keeping an eye of issues and problems (aka as 'bugs'). This guide should answer any questions you may have with the system. If it does not - then don't hesitate to contact us!

What is Bugtracker?

The Bugtracker is a secure web page system that makes it easy to keep track of any technical problems. To access the bugtracker login page, use a web browser and go to: www.fluffylogic.net/bugtracker/

Help! I can't log in.

If you can't log in because you don't have a users name and password, then you need to speak to your manager. You can also create a new account (i.e. get a user name and password - by clicking here:

If you have a user name but can't remember your pass work then - click here - and enter the information asked for and the system will re-send your password. If you have a user name and password but can't remember either then contact us and we'll sort that out for you.

I'm Logged In, How do I Use Bugtracker?

Once you log in, you will be presented with the following page:

This is the 'Main' page. From here you can navigate to other pages by clicking the mouse on the options. The ones you will find most useful are:

• My View

  This is a summary page of the current bug situation. This page lists all the bugs that are assigned to you, that are unassigned (i.e. nobody is down to look at them), that are reported by you, that are being Monitored by you can also lists the most recently modified bugs.

• View Issues

  This lists all the bugs in the system. You can alter the way this information is displayed to you by clicking on any of the column headings. For example if you click on the 'severity' column heading, it will list them in severity order.

• Report Issue

  This is where to click to enter the details about any error, bug or issue you have.

• Change Log

  This option is not currently required, so is not in use. Docs - This is where to find information on the bug tracker system and any related issues.

• My Account

  If you wish to change your password, email address or Real Name (not your username) then you can do it here. From here you can also access the 'Preferences' page (which allows you to change a number of options including how and when you get emails from bug tracker telling you of bugs). You can also access the 'Profile' option which allows you to enter data about the computer you normally use (as well as to set up new profiles) to that information can be factored into the bug fixing process.

How do I Report an Issue?

Once you have logged in, lick on the 'Report Issue' link. From here you will be taken to another page and asked to select the project that the bug relates to. (Tick the 'Make Default' box to ensure that you don't need to do this each time if all your work only related to one project.) Once Bug Tracker knows the project it will take you to the 'Enter Report' page. On this page fill in all of the information you can. The following guidance may help (remember all the data can be changed, so if you enter something incorrect or don't know what to put - it can always be changed/added later, so don't worry!):

• Category

  Simply select the area of the system that this error related to.

• Reproducibility

  This is how often you can get the bug to repeat. If it happens every single time you perform a set task, then it is 'always' and down the scale to if you only saw it happen once and could not get the bug to happen again ('unable to duplicate'). It is recommended that you try to get the bug to repeat, as the more information you can provide, the easier it is to fix the problem. If you are suggesting a new feature then select 'N/A'.

• Severity

  This is how nasty the bug is. Again, this is on a scale of responses from 'block' which is a major error that is stopping work from happening at all. A crash means your computer crashes when the bug occurs. In the middle is 'minor' which is when you can work around the problem, but it is annoying to 'trivial' which is a very minor issue that does not effect your work or the system in any tangible way, but is non the less a problem. Use 'feature' to suggest an improvement or change to the way the system works.

• Summary

  This is simply a few words that describe the problem. Please be descriptive here as simply saying 'database error' does not distinguish it from other problems. You must enter something into this box for the bug to enter the tacking system.

• Description

  This is what the bug is. The more information you can provide the better. Ideally here you will write a step-by-step description of how what actions lead to the bug occurring and what it looks like/causes when it does happen. You must enter something into this box for the bug to enter the tacking system.

• Additional Information

  If you have any ideas about what is causing the bug or any other information you think would help in identifying the problem and fixing it, then please provide it here.

• Upload File

  Use the 'browse' button to copy to the system any file that you think may help in sorting the problem. This is normally only used to upload a file which is needed to duplicate the bug, especially if that file is not one that is part of the main system and only exists on your computer.

• View Status

  Allows you to change the bug from public (so any database users can see it) to private (where only managers can see it). The default is public, which should be fine for most bugs.

• Report Stay

  Tick this box if you have another bug you wish to report following this one.