Why is/isn't my bug being worked on right away?
I'm playing devil's advocate here and asking the question: "Why has the bug I reported not been started on right away? Can't you fix it already?".
-
Like any software company, at ADM we have to fix lots of bugs during the development process in order to deliver stable and useful software.
Some bugs are trivial, others are complex. Some can be incredibly hard to unravel and take days to fix for us with only a tiny benefit to a minority of users (we don't like these ones!). Others are shallow and easy to fix and benefit the whole user base immediately.
We therefore work hard to categorise all the bugs reported to us so that we don't spend time looking at the wrong ones. At ADM, we believe a smaller development team yields better software and want to keep our team compact. For this reason, we try to keep things simple and work on the things that benefit the most people.
The severity and response levels we use are as follows:
1. CRITICAL
Critical bugs either render the Production software unusable or expose security vulnerabilities.
These bugs are to be addressed immediately in the next hot-fix release.
2. MAJOR
Issues which have significant repercussions but do not render the whole system unusable are marked major.
An example would be a .NET error which is only triggered under rare circumstances or which affects only a small percentage of all users.
Major priority is also used for tasks or features which ADM deems important (such as improving performance or code refactoring),
but which are not functional bugs. These issues are prioritised in the next full release.
3. NORMAL
Bugs that affect one piece of functionality are normal priority. This is a self-contained bug and does not impact
the overall functionality of the software or there is an easy workaround. These issues are noted and may be included in an upcoming release.
If a upgrade of that area of the software is planned, it is more likely the issue will be addressed later as part of the upgrade.
4. MINOR
Minor priority is most often used for cosmetic issues that don't inhibit the functionality or main purpose of the project,
such as layout or appearance of features or requests to add or change desired functionality.
These issues are noted and may be included in an upcoming release.
If a upgrade of that area of the software is planned, it is more likely the issue will be addressed later as part of the upgrade.
Please sign in to leave a comment.
Comments
1 comment