Lattica gives you a small set of standard fields out of the box and lets you add custom ones when you need them. The trick is using as few as possible.
Standard fields
Every task has these from the moment you create it:
- Title — keep it action-oriented. “Fix login redirect on Safari” beats “Login bug.”
- Description — Markdown supported, including code blocks, tables, and embeds.
- Assignee — exactly one person. If two people are responsible, neither is.
- Status — workflow position; defaults to Todo / In progress / In review / Done.
- Priority — Low / Medium / High / Urgent.
- Due date — date, optionally with time of day.
Priority — the rule of one Urgent
If everything is Urgent, nothing is. Lattica shows a soft warning when you mark more than three Urgent tasks at once. The intended ratio across a healthy backlog: 5% Urgent, 25% High, 50% Medium, 20% Low.
Priority drives default sort order on every view, and feeds into the Today dashboard which surfaces what to work on next.
Due dates and the calendar
Due dates can be a single date, a date with time, or a range (start → end). Range dates show as bars on the timeline view; single dates show as points on the calendar view.
Working hours and weekends are configured per workspace. Lattica won’t auto-shift due dates onto a weekend — but it won’t auto-skip them either. That’s a deliberate choice; we found auto-skipping caused more confusion than it solved.
Custom fields
Add fields per project, per task type, or workspace-wide. Supported types:
- Single-select dropdown
- Multi-select (tags-style)
- Number (integer or decimal, with unit suffix)
- Currency (with currency code)
- URL
- Person
- Date
- Formula (computed from other fields)
Resist the urge to add too many. Most teams that succeed with Lattica use 0-2 custom fields per project. The most common: Customer (person), Sprint (single-select), Estimate (number).
Required fields
You can mark any field as required for tasks to leave a particular status. For example, Estimate must be set before a task can move to “In progress.” Use sparingly — required fields are friction, and friction is sometimes warranted but usually isn’t.