http://bugs.thehunter.org
Registration
In order to use theHunter Mantis Bug Database you will need to have a registered account.
If you do not have an account PM NAOutdoors
You will be sent a validation email (remember to check your spam folder for this)
Account Validation
On completion of you registration you will have received a validation email containing a link that you must click on to validate your mantis account.
1. Follow the link sent to you in your validation email
2. You will be taken to a page containing your user information
3. Complete the required information (password) and click update user
4. Your account will now be validated and you will have access to Mantis.
IMPORTANT NOTE: After you have validated your account in order for you to have full access to our database you will have to wait for us to manually allocate you to the Hunter project. This can take up to 24hrs so please be patient. You will not be able to see any of the bugs or report any bugs during this time.
Viewing Bugs
Once we have assigned you to theHunter project the next time you login to Mantis you will notice the bugs are now visible. In order to view all of the bugs in the database you will select which project you would like to view the bugs in by the dropdown in the top right (theHunter Client by default):
1. theHunter Client - Game play bugs.
2. theHunter Web, Launcher & Support - All website related. Downloading, Updating, Patching, Logging in. Beta, Dev and Live Account issues.
Once a project is selected navigate to the 'View Issues Page' by clicking on 'View Issues' in the Mantis menu bar. You will be taken to a screen similar to this:
This is the 'View Issues' page and initially it will be un-filtered (showing all bugs). Before we talk about entering a new issue it is important that you know how to perform a search on the database just in case the bug you have found already has been entered by another beta tester:
Simple Search
One of the easiest and most effective ways to search the bug database is a text search. to do a text search is simple:
1. Locate the search box.
2. Enter some text you think relevant to your bug.
3. Click 'Search'
Shortly after you click search the list of bugs visible will change to reflect only bugs that contain the words that you used in your search. To clear the search and show all bugs again, click the reset filter on the far right side, along the same line as the search button.
Advanced Search
Of course there are many other ways to search the database for bugs that are more precise than a simple text search. By clicking on the + symbol next to the text search box the search filters will be displayed. The screen will look similar to this:
There are a number of different filters that can be used to refine your search. You can either use these separately or combine them in order to refine your search even more. To select a filter click on the available filter and then select what value you wish to filter by from the drop down list that is displayed.
An important note is to remember that any search you do will be remembered the next time you navigate to the View Issues page. So remember to view all issues you must reset your filter. This can be done by clicking reset filter.
Reporting a Bug
IMPORTANT NOTE: Please remember to always search for your bug before entering it into the database. The bug database contains many issues and there is a high chance that the bug you have found will have been found by someone else. It is important that we search the bug database in order to avoid the wasted time of a developer looking at a bug twice.
After a search of the database If you have not found your bug it is time to report it. Navigate to the 'Report Issue' page by clicking on the 'Report Issue' link in the Mantis menu bar. After a report has been made additional update may need to be made. How to do this can found in the The Beta Tester Bible.
It is important that you include ALL of the following information:
1. Project - Select whether the bug fits best in "thehunter Client" (game itself related) or "theHunter Web, Launcher & Support" (Website, Updating, Accounts).
2. Category - Select the category that most accurately describes your bug.
3. Reproducibility - How often does the bug occur? (Ideally test to see if the bug occurs several times before reporting it to get an idea of how often the bug occurs)
4. Product Version - The version of the game you found the bug on.
5. Summary - Short summary of your bug (Please be a descriptive as possible)
6. Description - More detailed description of your bug, please also include step by step guide of how to reproduce your bug.
7. Additional Information - If required (If creating the bug from a forum report, include the link to the bug topic on the forum)
8. Upload File - Please upload a screen shot if your bug is a graphical issue or any other files you think we may find useful when trying to reproduce the bug here.
After each of the above fields has been completed click on the 'Submit Report' button to report your bug. Your bug will now be in the database ready for a member of the EW development team to confirm.
The Bug Flow - What do all those different Colors Mean?
By now you will have noticed that each bug is highlighted in a certain color. Let me describe how the bug flow works.
1.
- On entry a bug will be highlighted red in the database. The bug will remain in this sate until a member of the dev team has had the chance to confirm the issue occurs.2.
- When a bug has been confirmed by the dev team it will be assigned, it will turn Blue.3.
- When a bug has been fixed it will be set to Resolved (Green). When one of your bugs has been set to this state it is important that you check the bug has been fixed on the next version of the game and If you agree the bug has been fixed then add a note to it confirming you confirm the fix.4.
- When a bug has been closed (either confirmed fixed or waived) it will turn grey and will not be included in searches unless otherwise stated in the search filters.5.
- If a bug has been set to Feedback it requires further information from the reporter. Usually this is due to the fact that EW is unable to reproduce the bug and require further steps to help them from the bug reporter.6.
- bug has been looked at but not confirmed or assigned