We have moved over to Bugzilla for all our feature and bug tracking. And we have decided to make it open to clients that have current support contract with us. This is something we have not done before, in the past we used something called Fogbugz for feature and bug tracking, but it was used internally only.

That means anyone with current support, can see upcoming features, and vote for them. We also have enabled posting new bugs/features, at least for now, we will be evaluating whether this is better than forcing to always report bugs to support or not. If there is some bug that affects you, just vote on it as a way to say "I need this fixed too" (just make sure it is same problem!) Or if there is some feature you would like added, vote on it as we will be using the votes to determine how popular a feature is.

Bugzilla Location: https://geodesicsolutions.com/bugzilla/

To log into Bugzilla, use the same username and password as you use to log into the client area on our site, typically this is your e-mail used when you purchased the software, and the password you entered at that time. That is the same login you will use to download the software, or to view the helpdesk. If you do not know or have lost your password, use the lost password link on the client area login page to have a new password e-mailed to you. If you still have trouble, contact [email protected].

You will need Active Support to be able to log into Bugzilla, as it is an advanced support related service. If you do not have active support, you can log into the client area to renew your support and updates for your license.

There are a few basics you may need to know for Bugzilla to make more sense.

• All issues are called bugs in Bugzilla, even new features¹⁾. If someone refers to "bug 123" that could be a bug in the software, or a feature. You can tell which it is by looking at the Importance for that bug, a feature will be marked with "enhancement". <
• Voting: If you see a feature that you would like added, you can vote on that feature. We use votes as a way to tell how much a certain feature is "in demand", if a feature has a lot of votes, there is more chance we will add it. Or if there is an issue that affects you, you can vote on the bug for that issue as a way to say "this affects me too". You will be notified of changes to bugs you have voted for²⁾. <
• Get Notifications of Changes: To get updates when changes are made to a bug, either vote on that bug if applicable, or you can add yourself to the CC List. When you are looking at a particular bug, near the top on the right should be an option to Add me to CC list, check the box and click the button to save changes³⁾. <
• Creating new Bug: You are welcome to create a new bug (for a feature or an actual bug), but first do a search to make sure it is not something already in the system. Also as you are typing in the title of the bug, it will list "similar" bugs it finds, make sure to look through the list as well. <
• Bug Status: All new bugs start out with status of UNCONFIRMED. This just indicates that the bug was created by a client and has not been "confirmed" by someone at Geodesic Solutions yet. Only Geodesic Solutions staff can change the status of a bug. Inside Bugzilla there is an explanation of different statuses.
  • Features: When a client adds a feature, it is considered a "feature request".
    • If we change the status to CONFIRMED, that means we have accepted that feature as a possible feature to be added, that does NOT guarantee it will be added soon, or even added at all. Once it is confirmed, we will wait to see how much demand for that feature there is (going by votes on the feature). <
    • If we change the status to anything else, such as RESOLVED WONTFIX, that means we feel that the feature is not something we feel should be in the software. For instance if you requested something like "add forums built into the software", most likely we will not accept that as it does not relate to the software; if you requested "Integrate with forum software XYZ" however, that may be something we would accept. <

<

• Actual Bugs: If you feel you have found a bug, you are encouraged to start a new bug for it. We will try to duplicate the problem as best we can, if we are not able to we'll change status to "WORKSFORME" you may need to provide additional information so we can figure out how to duplicate the problem. In some cases we may need you to start a support ticket so we can see the problem in action on your website. <

<

• Finding Things: There are quite a few ways to find what you want. See the Quick Tour for 6.0 section below for a few searches you can use to find certain things specific to the upcoming 6.0 release. Instead of repeating what is already in the Bugzilla documentation, just take a look at the quick search help page in Bugzilla. <
• Version VS. Target Milestone: In Bugzilla, the version is the version of the software that the bug was found in, not the version to be fixed or added in. For features, the version does not apply as much so does not matter what it is set to. The target milestone is the target Geo version the bug will be fixed or added in. Keep in mind it is the target, and not guaranteed. If a bug is not resolved yet, it is subject to change to later target milestone if needed. Note that only Geo staff can set or change the target milestone. See the bugzilla bug fields help for complete description for these or any of the bug fields. <

First make sure you read over the Things to Know section above. We'll give you a quick tour of the upcoming version 6.0.0. If 6.0 has already been released, you can replace 6.0.0 with whatever the next "upcoming release" is. Below we will list something to enter in the search (with a direct link to that actual search), and explain what each search is showing you.

• List of Finished Bugs⁴⁾ for 6.0.0: Search for FIXED milestone:6.0.0 <
• List of Remaining Bugs⁵⁾ for 6.0.0: Search for milestone:6.0.0 - NOTE: Any bugs⁶⁾ that are not resolved yet are not guaranteed to be added in 6.0.0. In other words, this is a list of things that "may" be added in 6.0.0 but we may elect to push a few of them off to a later version in order to release 6.0.0 sooner. <
• List of "In Progress" Bugs⁷⁾ for 6.0.0: Search for IN_PROGRESS milestone:6.0.0 - In progress means a developer has started working on that bug. Typically we will only mark a bug "in progress" if it is taking more than a day to complete. <
• List of All Bugs⁸⁾ for 6.0.0: Search for ALL milestone:6.0.0 <
• List of bugs⁹⁾ in future versions: Search for milestone:"future release" - NOTE: As mentioned in Things to Know, a feature that is listed as CONFIRMED does not guarantee that we will add it, just that it is something we may possibly add in the future. <