Pick the bug type below. Follow the steps. Better reports = faster fixes.
A button, form, or feature is broken. The most common bug type.
The bug form opens. First, give it a short title -- what broke in a few words.
Say WHAT is broken and WHERE. "Save button on job form" is better than "button broken".
This tells the developer it's a functional issue -- something that should work but doesn't.
Critical = nobody can work (app crashes, data lost)
High = important feature broken (can't save, can't submit)
Medium = something wrong but there's a workaround
Low = minor annoyance, not blocking anyone
The form shows you prompts. Just fill in the blanks. This is the most important part.
Without "What I did", the developer can't reproduce the bug. Without "What happened", they don't know what's wrong. Without "What I expected", they don't know what right looks like.
A picture is worth a thousand words. Three ways to add one:
Easiest: Press the Print Screen key on your keyboard, then Ctrl+V in the screenshot area.
Or: Drag an image from your files into the box.
Or: Click "Choose File" and pick an image.
If you see an error message on screen, ALWAYS screenshot it. The exact error text helps the developer find the problem 10x faster.
The bug gets a number (BUG-011, BUG-012, etc.) and appears in the list. The developer will see it and start working on it.
Layout broken, text cut off, colors wrong, things overlapping. It works, but it looks bad.
Say what looks wrong and where you see it.
Severity for cosmetic bugs is usually Low or Medium. Only use High if it makes the page unusable.
The developer needs to SEE what you see. A screenshot saves 10 minutes of guessing.
For cosmetic issues, a screenshot is almost required. Without it, "it looks wrong" means nothing -- the developer needs to see exactly what you see on YOUR screen.
Pages take too long to load, buttons freeze, spinners that never stop.
Severity: High if it blocks work. Medium if it's annoying but you can wait.
Count "one Mississippi, two Mississippi" or look at a clock. "30 seconds" is much more useful than "a long time".
Numbers don't add up, wrong information displayed, missing records.
Data bugs are usually High or Critical -- wrong data means wrong business decisions.
Always include the job number, customer name, date, or any other way to find the exact record. "An invoice" is not enough -- we need to find the SAME one you're looking at.
Can't log in, locked out, seeing things you shouldn't, permission errors.
These are usually High or Critical -- if you can't get in, you can't work.
Always copy the exact error message -- don't paraphrase. "Invalid credentials" and "Access denied" are different problems with different fixes. Screenshot the error if you can.
If you can't log in at all, you might not be able to submit a bug report either. Send a message on Telegram with a screenshot and Angel will fix it directly.
| If you see... | Choose | Severity |
|---|---|---|
| Button/form/feature doesn't work | Something doesn't work | High |
| Text cut off, wrong colors, ugly layout | Looks wrong | Low-Medium |
| Page takes forever, spinner won't stop | Too slow / freezes | Medium-High |
| Wrong number, missing data, bad total | Wrong data shown | High-Critical |
| Can't log in, 403 error, locked out | Login / access issue | High-Critical |
| Not sure what type it is | Something doesn't work | Medium |
If you can't decide which type, just use "Something doesn't work" and Medium severity. The developer can re-classify it. A slightly wrong category is much better than no bug report at all.