Recommended prefixes for Issue titles

[adamantmm]

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

Common prefixes

• [Bug] — for bugs, crashes, unexpected behavior
• [Feat] — for new functionality
• [Enhancement] — for improvements of existing features
• [Refactor] — for code refactoring without changing functionality
• [Docs] — for documentation, guides, or README updates
• [Test] — for adding or improving tests
• [Chore] — for routine tasks (dependencies update, CI/CD adjustments, etc.)

Project-specific prefixes

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

Ideas and proposals

• [Proposal] — formal proposal for changes
• [Idea] — an idea to consider or discuss further
• [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

👉 Please use one or two prefixes maximum to avoid overloading the title.

[al-onyxprotocol]

Hi!
This helps to get a quick overview in the issue list. ✅

[adamant-al]

Changed UI/UX ⟶ UX/UI to match with labels.