Documentation
Work plan hierarchy
unlimitedWEBSITES projects include a five-level work plan: a tree you can expand, collapse, and manage from the project dashboard. Higher levels are optional—you can add parentless Issues, Epics, Chapters, Epochs, or Portfolios, and nest only when it helps. Each project can set a default level for quick-add. An Issue is not separate from a support ticket: every Issue is backed by exactly one Firestore ticket (same approval rules, Kanban board, and thread). Portfolio–Epic rows are planning containers only.
| Level | Name | Role |
|---|---|---|
| 1 | Portfolio | Root container for all planned work on the project |
| 2 | Epoch | Long horizon (quarter, launch phase, "era") |
| 3 | Chapter | Major milestone arc inside an epoch |
| 4 | Epic | Large deliverable (familiar from JIRA) |
| 5 | Issue | Leaf work — story, bug, or task (extensible later) |
Tree view
On any project, open the Work plan tab to see work as an expandable tree. Higher levels are optional: you can create a parentless Issue, Epic, Chapter, Epoch, or Portfolio without building the full chain. Use + on a row to add the next level underneath (Epic → Issue). When you do nest, each child must be exactly one level below its parent.
Set a Default new item per project (for example Issue for ticket-only teams, or Epic for roadmap-first teams). The primary + button and empty state use that default.
Issue types
Level 5 items are always Issues. Pick a type when you create them; more types may be added later.
- Story — User-facing or product work described as an outcome or narrative.
- Bug — Something broken or incorrect; synced tickets use higher priority and the technical department.
- Task — Operational or internal work that is not necessarily user-story shaped.
Issues are support tickets
An Issue is a support ticket — not a separate item. Adding an Issue creates the ticket (or links an existing one). Client and staff approval rules apply before work can start, same as the Tickets tab. The work plan shows hierarchy; replies and Kanban use the ticket. We do not delete Firestore tickets after migration: they still hold the conversation and workflow data.
| Issue status | Ticket column |
|---|---|
| Backlog | Ticket: Open |
| To do | Ticket: Open |
| In progress | Ticket: In progress |
| Done | Ticket: Resolved |
Projects with client or staff approval gates may place new tickets in "Waiting for approval" before work starts—that is independent of the issue backlog status.
Getting started
- Sign in and open a project from your dashboard.
- Select the Work plan tab and add your default item type (often Issue or Epic).
- Optionally nest with + under a parent, or add other levels from the toolbar.
- Switch to Tickets to collaborate on the linked ticket threads.
Part of free project management on unlimitedWEBSITES—boards, organizations, and approvals at no per-seat platform fee.