Skip to main content

Feature Requests

Feature requests let the team submit and track product ideas. There are two surfaces: a quick-submit popover available from the header, and a full management page.

Submitting a request (header popover)

The lightbulb icon in the header opens a small popover:

  • A textarea for the request description (placeholder e.g. "Export collections as CSV…").
  • Enter submits; Shift+Enter inserts a newline. There's also a Submit button.
  • On success it shows "✓ Request submitted — thank you!" and closes after a moment.
  • A View all requests link jumps to the full page.

Submitting POSTs to /api/feature-requests with just the description — the submitter is recorded from your session.

Feature Requests page

Route: /feature-requests

A table of all requests from the team.

Filters

  • Status dropdown — All, or any single status.
  • Hide implemented checkbox — on by default, so the list focuses on open work.
  • A live count of visible requests on the right.

Table

ColumnContents
DescriptionThe request text (wraps)
Submitted byThe submitter's name
DateCreation date; hover shows the implemented date if applicable
StatusA status badge (an editable dropdown for admins)
(actions)A trash icon to delete

Statuses

Requests move through this lifecycle:

StatusColourMeaning
ReceivedslateNewly submitted
AcknowledgedamberSeen and accepted as a valid request
BuildingblueActively being implemented
ImplementedgreenShipped (records an implemented date)
DeniedredWon't be done

Admin actions

  • Admins see the status as an inline dropdown and can change it directly; setting it to Implemented stamps the implemented date.
  • Delete is available to admins on any request, and to the submitter on their own requests.

Non-admins see a read-only status badge and can only delete their own submissions.