An issue carries eight properties on its property rail: Status, Priority, Effort, Assignee, Project, Due date, Labels, and Visibility. The values below are the ones the shipped menus accept.

​
Status

Seven values, in workflow order. Grouping and board columns use the same seven.

​
Priority

Four values. There is no explicit “none”; a new issue starts at Normal.

​
Effort

T-shirt sizing in five steps: XS, S, M, L, XL. An issue with no estimate reads No size. Effort is a sizing signal, not a commitment.

​
Visibility

​
Assignee, Project, Due date, and Labels

Assignee defaults to Unassigned and stays that way until someone is on the hook. Project links the issue to one project, which decides where it is grouped in the plan. Due date is empty until you set one, and once set feeds the overdue and upcoming buckets. Labels accepts multiple labels, stacked as color dots on the pill.

​
Filtering by property

The filter control on any issue view filters on seven of the eight properties: Status, Assignee, Priority, Labels, Due date, Project, and Visibility. Effort is not filterable. Every view and filter combination lives in the URL, so a configured view is a link you can share.
  • Issues: how issues move through the workflow, and what views and filters can do.
  • Terminology: the words Bright uses, and what each one actually refers to.
  • Troubleshooting checklist: what to check when a run does not behave.