When adding a task inline on a project's board or list, you can type structured tokens directly in the task name field. Fishladder parses them in real time and shows color-coded chips below the input. The remaining text becomes the task title.
| Token | Syntax | Example | Effect |
|---|---|---|---|
| Assignee | @name | @sarahchen or @sarah | Assign the task to the matching team member (see below) |
| Priority | !level | !high | Set priority — !low, !medium, !high, or !urgent |
| Due date (relative) | due:word | due:friday | Set a relative due date |
| Due date (absolute) | due:YYYY-MM-DD | due:2026-04-01 | Set an exact due date |
| Project | >project-name | >mobile-app | Create the task on another project (see below) |
| Tag | #tagname | #backend | Reserved — removed from the title but not applied yet (see below) |
@ matches a team member in one of two ways (case-insensitive):
@sarahchen for Sarah Chen.@sarah works if there is one Sarah on the team.If two teammates share the first name, or nobody matches, the chip is shown as unknown and the task is created with no assignee — Fishladder never guesses. Use the full name instead. Only the first @ token is used.
> takes the project's name in lowercase with spaces replaced by hyphens — a project called "Mobile App" is >mobile-app. The task is created on that project in its default status, with no category. Archived projects are not matched. If the name matches no project, the chip is shown as unknown and the task is created on the project you are in.
#tags are reserved and not applied yet. Fishladder recognises them, shows a chip, and removes them from the title, but the new task is created without tags — tasks do not have a tag editor yet.
The due: token accepts several relative date keywords (case-insensitive):
| Keyword | Resolves to |
|---|---|
today | Today |
tomorrow | Tomorrow |
monday – sunday | Next occurrence of that weekday (always in the future — due:friday on a Friday means next Friday) |
nextweek | Monday of next calendar week |
nextmonth | First of next month |
A due: value that is not one of these keywords or a valid YYYY-MM-DD date is removed from the title and sets no due date.
Tokens can appear in any order and can be mixed freely with the task title. For example:
Fix login bug @sarah !high due:friday >mobile-appThis creates a task titled "Fix login bug" on the "Mobile App" project, assigned to Sarah (if she is the only Sarah on the team), with high priority, due next Friday.
As you type, parsed tokens appear as colored chips below the input:
@name)#name, not applied)>project-name)Click the × on any chip to remove that token from the input.
If your input contains no tokens at all, task creation works identically to before — just type a title and press Enter.