Recommended prefixes for Issue titles

To keep Issues clear and consistent across the ADAMANT organization, use short prefixes in the title when creating a new Issue. This helps everyone quickly understand the type of task at a glance.

Common prefixes

Use [Bug] for bugs, crashes, or unexpected behavior. Use [Feat] for new functionality and [Enhancement] for improvements to existing features. Use [Refactor] for code refactoring that does not change functionality. Use [Docs] for documentation, guides, or README updates. Use [Test] for adding or improving tests. Use [Chore] for routine tasks such as dependency updates or CI/CD adjustments.

Project-specific prefixes

Use [Task] for a general task that may not be directly related to coding. Use [Composite] for a task that includes multiple subtasks. Use [UX/UI] for user interface or user experience changes.

Ideas and proposals

Use [Proposal] for formal proposals, [Idea] for ideas to consider or discuss further, and [Discussion] for topics that may require wider input. However, the best place for these three is the ADAMANT forum rather than Issues.

Examples

[Bug] Crash when syncing wallet on iOS
[Feature] Add support for biometric auth
[Docs] Update installation guide for Ubuntu 24
[Refactor] Split TradeBot config module
[Composite] Add decentralized file transfer across ADM messenger apps
[UI/UX] Improve Home screen design
[Task] Release iOS app v3.10.1 to the App Store

Use one or two prefixes maximum to avoid overloading the title.