Management & Status
Manage suggestions through a complete 9-status lifecycle. Every status change updates the Discord embed, records an audit entry, and notifies the suggestion author via DM.
Status Lifecycle
Suggestions move through a structured lifecycle with enforced transition rules. Each status has a dedicated emoji, color, and label displayed on the suggestion embed.
💡 New
InitialEvery suggestion starts here when submitted via /suggest or the dashboard.
Can transition to: Under Review, Accepted, Declined, Duplicate, Archived
🔍 Under Review
ProcessingStaff is actively evaluating this suggestion. Shows the community that feedback is being considered.
Can transition to: Needs Info, Accepted, Declined, Duplicate, Archived
❓ Needs Info
WaitingStaff needs more details from the author before making a decision. The author is DM'd with the reason.
Can transition to: Under Review, Accepted, Declined, Duplicate, Archived
✅ Accepted
ApprovedThe suggestion has been approved and will be implemented. A major milestone for the suggestion author.
Can transition to: In Progress, Declined, Archived
🔨 In Progress
ActiveWork has started on implementing this suggestion. Keep the community engaged with progress updates via the reason field.
Can transition to: Implemented, Accepted (revert), Archived
🎉 Implemented
DoneThe suggestion has been fully implemented. Include details about what was added and where to find it.
Can transition to: Archived
❌ Declined
RejectedThe suggestion won't be implemented. A reason is required when declining to help the community understand the decision.
Can transition to: Under Review (reconsider), Archived
🔁 Duplicate
MergedThis suggestion duplicates an existing one. The reason field should reference which suggestion it duplicates.
Can transition to: Under Review (if original was wrong), Archived
📦 Archived
StoredPermanently archived. Can be restored to New if needed in the future.
Can transition to: New (restore)
Staff Commands
The /suggestion command requires Manage Server permission and provides 7 subcommands for complete lifecycle management.
/suggestion accept
/suggestion accept id:<suggestion> [reason:"Why it was accepted"]Moves a suggestion to Accepted status. Author receives a DM notification. The original embed updates with the new status.
/suggestion decline
/suggestion decline id:<suggestion> reason:"Why it was declined"Moves a suggestion to Declined status. Reason is required to provide transparency. The reason is included in the author's DM and displayed as a "Staff Notes" field on the embed.
/suggestion implement
/suggestion implement id:<suggestion> [reason:"Implementation notes"]Marks a suggestion as Implemented. Use the reason field to describe what was built and where to find it.
/suggestion review
/suggestion review id:<suggestion> [reason:"Review notes"]Moves a suggestion to Under Review. Also used to reopen declined or duplicate suggestions for reconsideration.
/suggestion progress
/suggestion progress id:<suggestion> [reason:"Progress notes"]Marks a suggestion as In Progress. Use the reason to share development progress or estimated timelines.
/suggestion duplicate
/suggestion duplicate id:<suggestion> reason:"Duplicates suggestion #abc123"Marks a suggestion as Duplicate. Reason is required — reference the original suggestion so the author knows where to follow progress.
/suggestion info
/suggestion info id:<suggestion>View detailed information about a suggestion including status, board, category, author, full vote breakdown (upvotes / downvotes / score), and source.
Autocomplete: All id: fields support autocomplete. Start typing a suggestion title or keyword and matching suggestions appear in the dropdown.
Status Transition Rules
Not all status transitions are allowed. The system enforces logical progression to maintain data integrity. Invalid transitions return a clear error message.
What Happens on Status Change
When a staff member changes a suggestion's status, three things happen automatically:
Author DM Notification
The suggestion author receives a DM with the new status, their suggestion title, and the staff reason (if provided). If the author has DMs disabled, this is silently skipped.
Embed Update
The original suggestion embed in the Discord channel is edited to reflect the new status emoji, color, and label. If a reason was provided, it appears as a "Staff Notes" field on the embed.
Audit Trail
Every status change is recorded in the audit log with the actor, timestamp, from/to statuses, and reason. Viewable in the web dashboard.
Management Best Practices
Always include reasons
Especially when declining — clear reasoning builds community trust and helps members submit better suggestions
Review regularly
Schedule weekly reviews to move pending suggestions through the pipeline. A stale queue discourages participation
Use the full lifecycle
Moving suggestions through Under Review → Accepted → In Progress → Implemented shows the community their ideas are taken seriously
Mark duplicates promptly
Consolidate duplicates early and reference the original so authors can follow the right suggestion
Archive completed suggestions
Once implemented, archive suggestions after a period to keep the active board focused on new ideas