Explaining when to use "bug", "feature", "improvement", or "chore" labels while working on an IT project.
- Use "bug" when the change restores expected behavior that is broken: e.g., fixing a checkout crash, correcting a wrong output value, or patching a security vulnerability.
- Use "feature" when the change introduces a new end-user capability: e.g., adding a wishlist, launching a new payment method, or delivering a fresh API endpoint.
- Use "improvement" when the change enhances existing functionality without altering core behavior: e.g., optimizing image loading, refining UI, or upgrading internal tooling.
- Use "chore" when the change involves operational maintenance or configuration with no direct user or performance value, such as updating dependencies, adjusting build scripts, or performing housekeeping tasks.
What is "Bug"?
- Regressions that break a previously working flow
- Crashes, errors, or incorrect outputs that users can reproduce
- Security or compliance gaps needing immediate correction
What is "Feature"?
- Brand-new user journeys or screens
- Additional integrations or supported payment/shipping methods
- Fresh backend capabilities exposed to clients
What is "Improvement"?
- Performance boosts or scalability tuning
- UI/UX refinements to existing components
- Developer-experience upgrades like tooling or test coverage
What is "Chore"?
- Routine maintenance tasks that are required to keep the codebase healthy
- Configuration updates to CI/CD pipelines, servers, or environments
- Dependency upgrades or library patches (that are not security critical)
- Administrative tasks like writing internal wikis or organizing file structures
tale