Status Management¶

!!! info "TL;DR" Submissions follow a 7-status workflow: Open → Under Review → Planned → In Progress → Shipped / Declined / Merged. Every status change is logged in the status history audit trail.

Submission Lifecycle¶

Submissions move through a defined lifecycle from creation to resolution. Each status represents a stage in the product team's decision-making process.

Status Workflow¶

Open
  ↓
Under Review
  ↓
Planned  OR  Declined
  ↓
In Progress
  ↓
Shipped  OR  Merged

Status Definitions¶

Changing Status¶

From Submission Detail Page¶

1. Open the submission (/submissions/[id])
2. Click the Status dropdown (top-right)
3. Select new status
4. Optionally add a comment explaining the change
5. Click Update Status

The status change is saved and users following the submission are notified.

From Triage Queue¶

1. Navigate to Admin → Triage Queue
2. Find the submission in the list
3. Click the Quick Status dropdown
4. Select new status (no comment required)

For bulk status changes, see Triage & Moderation.

Status History¶

Every status change is recorded in the status_history table. The history includes:

• Status — New status value
• Changed By — User ID of admin who made the change
• Timestamp — When the change occurred
• Comment — Optional explanation for the change

View status history on the submission detail page in the "Timeline" sidebar.

Example Status History¶

Status-Specific Behavior¶

Open¶

• Visibility — Public, appears in main submission list
• Notifications — Author is notified on creation
• Next Steps — Admin should review and change to "Under Review" or "Declined"

Under Review¶

• Visibility — Public
• Notifications — Author is notified when status changes to "Under Review"
• Next Steps — Team evaluates feasibility, votes, and sentiment; moves to "Planned" or "Declined"

Planned¶

• Visibility — Public, appears in roadmap view
• Notifications — Author and followers are notified
• Next Steps — When development starts, change to "In Progress"

In Progress¶

• Visibility — Public, appears in roadmap under "In Progress"
• Notifications — Author and followers are notified
• Next Steps — When released, change to "Shipped"

Shipped¶

• Visibility — Public, appears in roadmap under "Shipped"
• Notifications — Author and followers are notified with release notes link (if provided)
• Next Steps — Submission is considered complete; no further action needed

Declined¶

• Visibility — Public, but not shown in main list by default (users can filter for "Declined")
• Notifications — Author is notified with optional explanation
• Next Steps — Submission is closed; no further action needed

Merged¶

• Visibility — Redirects to primary submission (users never see "Merged" submissions directly)
• Notifications — Author is notified that their submission was merged
• Next Steps — Votes and comments are transferred to primary; no further action needed

Status Change Notifications¶

When a status changes, notifications are sent to:

• Submission Author — Always notified
• Followers — Users who voted or manually followed the submission
• Team Members — Admins who commented on the submission (optional, configurable)

Notification channels:

• In-App — Notification badge in header
• Email — Digest email (daily or weekly, user-configurable)
• Webhook — For external integrations (e.g., Slack)

See Settings for notification configuration.

Bulk Status Changes¶

Admins can change the status of multiple submissions at once:

1. Navigate to Admin → Triage Queue
2. Select submissions using checkboxes
3. Click Bulk Actions → Change Status
4. Select new status
5. Optionally add a comment (applied to all selected submissions)
6. Confirm

All selected submissions are updated and notifications are sent to followers.

Use Cases for Bulk Status Changes¶

• Roadmap Planning — Bulk move submissions from "Under Review" to "Planned"
• Sprint Start — Bulk move submissions from "Planned" to "In Progress"
• Release Day — Bulk move submissions from "In Progress" to "Shipped"
• Cleanup — Bulk move stale "Open" submissions to "Declined"

Status Automation (Future)¶

Upcoming feature: Auto-update status based on GitHub issue state.

Example rules:

• If GitHub issue status = "In Progress" → Canviq status = "In Progress"
• If GitHub issue is closed → Canviq status = "Shipped"
• If GitHub issue is labeled "wontfix" → Canviq status = "Declined"

Enable automation in Admin → Settings → GitHub Integration.

Status Metrics¶

Track status distribution over time:

• Status Breakdown — Count of submissions in each status
• Avg Time in Status — Median time from creation to "Shipped"
• Status Velocity — Submissions moved per week

View metrics in Admin → Analytics → Status Metrics.

Example Status Breakdown¶

Example Time in Status¶

Use these metrics to identify bottlenecks (e.g., submissions sitting in "Planned" for too long).

What's Next¶

• GitHub Integration — Push feedback to GitHub and sync status
• Triage & Moderation — Review and categorize submissions
• Settings — Configure notification preferences