Floumy Documentation

Issues and Requests

Capture bugs and customer demand, search and prioritize the backlog, and connect feedback back to delivery.

Requests

Requests are for feature demand, product feedback, and customer ideas.

What a request contains

  • Title
  • Description
  • Vote count
  • Status
  • Optional estimation
  • Related initiatives
  • Comments

Request statuses

Status
Pending
Approved
Planned
Ready to Start
In Progress
Completed
Closed

What users can do on the Requests page

  • Search requests by title or description
  • Vote up or down on requests
  • Open request detail pages
  • Create new requests

Request detail pages

Request detail pages show:

  • The request content
  • Related initiatives
  • Comments

From the admin edit screen, you can also:

  • Change request status
  • Set an estimation
  • Delete the request
  • Generate initiatives with AI based on the request title and description

Issues

Issues are for bug reports and operational defects.

What an issue contains

  • Title
  • Description
  • Status
  • Priority
  • Related work items
  • Comments

Standard issue statuses in the edit screen

Status
Submitted
Acknowledged
Under Review
In Progress
Awaiting Customer Response
Resolved
Closed

Priority levels

Priority
Low
Medium
High

What users can do on the Issues page

  • Search issues by title or description
  • Review issue statistics
  • Open issue detail pages
  • Create new issues

Issue detail pages

Issue detail pages show:

  • The current issue status and priority
  • Related work items
  • Comments

Use the link to work items whenever a bug has an execution trail you want the team to track.

Public Feedback Flows

Requests and issues can also be exposed on public project pages when build-in-public is enabled.

Important behavior:

  • Public visitors can browse public request and issue boards without signing in.
  • Creating a new request or issue requires authentication.
  • Commenting also requires authentication.

This makes it possible to expose intake publicly without allowing anonymous editing.

When to Use Each

Use Requests when…Use Issues when…
You are collecting ideas, demand signals, or product suggestionsYou are tracking a defect, regression, or broken workflow
You want votes to help prioritizeYou need a clear bug lifecycle with status and priority
You may turn customer demand into initiatives laterYou may turn a fix into work items immediately