At Web Engineer I look after a wide range of sites, from the single brochure style site for a boutique hotel to the more complex, which require consistent data and content updates.
Occasionally the customer can encounter a bug where a part of the site isn’t working the way it should; these things do happen from time to time, normally as a result of a change or site update.
If you’re in a situation where you’re in the office and need support, think about how you would provide us with information. Here’s a good and bad example of how to write the subject line of the Helpdesk message your busy support team:
Always think about how you would describe the issue in as few words as possible and quickly and uniquely identify what the bug is, why do this you ask? Well, it helps explain things clearly. Even if you’re not an expert a few extra words to explain what you see helps your support identify what the problem is.
Now onto the bug report itself, firstly figure out the steps to reproduce the bug – by providing us with as much information as possible will mean that we can identify and rectify the problem much quicker than struggling to reproduce the bug due to unclear instructions.
2. Clearly outline the steps to reproduce the bug. E.G
3. Outline the expected result and the actual result (what’s meant to happen vs what actually happened)
4. Include any other asset or information you think may help