Have you ever noticed how the majority of the updates you get for apps reference little more than "bug fixes"?
The very best software is continually moving forward, getting refined, introducing new features, removing defunct features, getting quicker, faster... The world has changed and no one wants to be using software that doesn't change from one year to the next, losing pace with changes to the industry or audience it's serving.
This is why we at CMAP introduce a new version, every two weeks. A new version with enhancements to existing features, brand new functionality and performance improvements.
Like all other fresh and modern, forward-thinking software applications, innovation comes with the odd bug here or there. But what exactly is a bug?
A software bug is an error or fault in the program that causes an unexpected result or for it to behave in unintended ways. Most bugs arise from errors in the code or design, or through changes to external components e.g. web browser updates.
All software applications have bugs—even old school locally hosted applications that are lucky to get a new version once a year, let alone every two weeks, all the way through to the big hitters of Twitter, Instagram and Google, who have armies of development teams! And CMAP is no exception.
Thankfully, we are able to respond quickly and decisively when these bugs rear their heads, fixing the overwhelming majority of them in less than two weeks.
Fixing bugs can be slow work when there's little information to go on. Which is why we ask that you provide us with the following information:
- Error Ref: If an Error Ref is created (a bug may not have one as it may, strictly speaking, not have "errored"), copy + paste it into your request, as this helps us track down the issue
- Specific Data: Any specific data e.g. project numbers, invoice numbers, affected users, etc., that will help us track down what caused the issue
- Steps Taken: A quick explanation of what you were doing in the build up to the error occurring, as this helps us make sense of the possible entry points at which it may have crept in
- Screenshot (if relevant): The majority of the time a screenshot isn't required, but sometimes it can really help us get to the bottom of it, especially when there's no Error Ref
We appreciate bugs are an inconvenience and you're in the middle of something when they take place, so we're not asking for a thousand word thesis, just a few key details that will help us eliminate the bug as quickly as we can for you, even if they're just bullet point-like sentences.
Here's a great example:
With that, we'd have the Error Ref (if there was one), the user, the affected area of the application and a specific example to look at, plus an explanation of the steps that led to the bug. Providing even just this amount of detail will help us eliminate these pesky critters on the double!
Thank you for your support and understanding!