Items and projects

Projects are the top-level containers in LFG List. Items live inside projects.

An item can include:

• A title.
• A rich text description.
• A status.
• Labels, priority, assignees, due date, and recurrence when those features are enabled for the project.

Projects

Use projects to separate work with different audiences, workflows, or automation needs.

A project usually works best when it represents one meaningful container:

• A product roadmap.
• A team backlog.
• A customer implementation.
• A personal operating list.

If two groups of work need different statuses, labels, permissions, or recurring patterns, they probably belong in separate projects.

Items

Items are the individual things you want to track. They can be tiny tasks, bugs, feature requests, chores, follow-ups, or planning notes.

Use the item title for the thing you want to recognize in the grid. Use the description for everything that helps someone complete or understand it.

Item details

Open an item when the grid row is not enough. The detail view is where you can edit longer descriptions and structured fields without losing the surrounding project context.

Common detail fields include:

• Description for supporting notes and links.
• Status for the current phase of work.
• Labels for classification.
• Priority for relative importance.
• Due date for time-sensitive work.
• Recurrence for items that repeat after completion.

Practical guidance

• Keep item titles short and action-oriented.
• Use descriptions for context, links, notes, and supporting detail.
• Use labels and filters when a project grows beyond a simple list.
• Use project settings to shape the workflow instead of creating multiple similar projects.

Finding the right items

Use search and filters when a project grows. Filters are meant to narrow the current view, not permanently change the project.

If a view is empty and you expected items, clear the filters and check whether you are in Active, Complete, or Trash.