Why bugs vs feature requests
Why bugs vs feature requests
Ailaaj One separates bugs from feature requests so the right team can act, and so Academy documentation stays honest about what shipped.
Bugs
A bug means the product should already do something correctly and does not. Fixes usually land as PATCH (or sometimes FEATURE polish) in product line versioning, show up under Fixed in What’s New, and may update an existing how-to when behaviour changes.
Feature requests
A feature request means you want something new or a material improvement to a working flow. Accepted work often bumps a FEATURE or MODULE version, appears under New / Improved in What’s New, and gets a new or expanded Academy guide.
Why the split matters for you
| You choose… | Team focus | Docs & release notes |
|---|---|---|
| Bug | Reproduce, fix, verify | Fix note + guide correction if needed |
| Feature | Prioritise, design, ship | New capability + guide when ready |
Mixing them up (calling a missing capability a “bug”) slows triage and can leave Academy paths out of date. When unsure, prefer the closer match and say so in the description — support can reclassify.