Clear, consistent task naming improves communication across development, marketing, and billing. Standardized prefixes make work easy to scan, prioritize, and report—whether you’re committing code, logging time, or preparing invoices. This guide defines the approved prefixes and the formatting rules for using them across all E19 Creative projects. Each prefix represents the type of work being performed and is followed by a short, descriptive summary.
Core Prefixes
| Prefix | Description |
|---|---|
| Bug | A confirmed defect or broken function that needs correction. |
| Issue | A general problem or anomaly under review. |
| Error | A logged or reproducible error condition. |
| Feature | A new function, capability, or system addition. |
| Enhancement | An improvement or extension of an existing feature. |
| Optimization | Performance or efficiency improvement. |
| Refactor | Internal code or structural reorganization without behavior change. |
| Maintenance | Routine upkeep, patching, or dependency updates. |
| Migration | Transition of data, environments, or systems. |
| Configuration | System or environment setup or parameter adjustment. |
| Integration | External connection or API implementation. |
| Investigation | Diagnostic or exploratory work to isolate a cause. |
| Task | General work item or administrative action. |
Optional Prefixes
| Prefix | Description |
|---|---|
| Review | Code, design, or documentation review. |
| Research | Technical or conceptual exploration. |
| Upgrade | Framework, platform, or dependency version update. |
| Deployment | Rollout or live environment release. |
| Patch | Urgent correction applied post-release. |
Usage Standards
- Format: Prefix | Brief Description – Optional Detail
Example: Feature | QR Code Tracking for Manuals – Summit Industries - Capitalization: Always capitalize the prefix and sentence-case the remainder.
- Scope: Use consistently across all internal systems, including development tracking, marketing task lists, and billing documentation.
- Clarity: Keep phrasing concise and action-oriented—avoid filler or abbreviations.
Example Usage
Bug | Validation Error in Registration Form – Correct Input Handling
Feature | Superuser Access Control – Add Role Permissions
Refactor | Membership Controller – Reorganize Function Order
Maintenance | JRE Update – ColdFusion 2025 Compatibility
Optimization | API Responses – Enable JSON Compression
Implementation Notes
- Use the pipe ( | ) separator for visual clarity across departments.
- Prefixes may be extended or combined for hybrid tasks (e.g., Enhancement | UI and Copy Update).
- Maintain consistency in naming for automated reporting and time tracking.
- Review this list quarterly as new categories or systems are introduced.
Posted in Technical Guides
