Skip to main content

New task

The new task form is where you describe a piece of work and choose how Jaah runs it. It opens beside the board when you select New task on the task board (+ on a phone), or Task in its ▾ menu. The same form, filled in, is the Task tab of every task page.

For the steps, see Start a task.

At the top right, ⤢ gives the form more room and ✕ closes it. The form has one tab, Task (not shown on a phone); the others appear once the task exists. With no project to file into yet, the form says No project yet — add one first. While the form is open, the browser tab reads Jaah | New task.

The new task form: the breadcrumb Mobile app › New task, the formatting bar, the description box, the size and involvement lists, Attach, Assigned to, From issue, Advanced, and Discard, Save and Go

The form​

ItemWhat it does
BreadcrumbThe project the task goes into, then the feature when you opened the form from one. Select either to change it. Under All projects, the project starts as the one you last filed a task in. Projects you hid aren't offered.
Formatting barBold, Italic, H1, H2, • List, 1. List, ☑ Checklist, a quote, Code, a code block, 🔗 Link and 🖼 Image. When the editor is narrow, the less used ones move under ⋯.
Description boxThe goal and any context: What needs to happen? A title is generated from it. Paste or drop screenshots straight in. Misspelled words are marked as you type, except in code.
Size listHow big the task is: Sketch, Task, Epic or Playbook. See Size.
Involvement listHow much the runner asks you: Unattended, Guided or Interactive. See Involvement.
AttachThe paperclip. Adds files to the task. Once it has files, 2 files beside it shows or hides them.
Assigned toWho the task is addressed to: its questions, alerts and the done notice go to them. It starts as you.
From issueFills the description from a Jira, Linear or Backlog issue and links the task to it: type its key or words from its title. If the description already has text, Replace or Keep mine asks first. When the project links no issue tracker, the field is greyed out; hover it for Link an issue tracker in project settings, where project settings opens the project's Settings tab at Issue trackers. See Start a task from a tracker issue.
AdvancedOpens the settings most tasks never need. See Advanced.

The size and involvement lists have no label of their own: each shows its current pick. Hover one for what that pick means, such as Task — one runner ships it as a merged PR. Your organization's settings choose what each starts on. When the form opens from a link that names a persona, a chip such as Researcher beside the size list says who runs the task. Someone who can only view a task sees the two as text instead: Depth and Involvement.

On a phone, From issue and a filled-in Assigned to move into Advanced; an empty Assigned to stays on the form, so the gap shows.

In a project whose Live Cast is on, an org owner or admin also sees the task's Live Cast camera in the header. It stays dimmed (Pending) until you pick Published or Hidden; the pick is set on the task when you select Save or Go. Shown only when your organization's plan includes Live Cast. See Task page.

Size​

PickMeans
SketchA quick mockup to look at. Picking it sets the involvement to Interactive; you can change it.
TaskOne runner ships it as a merged pull request. In a project with no repository, the runner does it and reports back.
EpicAnalysed and split into subtasks first. See Start an epic.
PlaybookRuns one of your organization's playbooks. Shown only when your organization's plan includes Playbooks. See Run a playbook on a task.

The form with Epic picked in the size list, and Guided in the involvement list

Playbook opens a menu of your organization's playbooks, each with its description. One that can't run yet is greyed out with the reason. With none yet, the menu says No playbooks yet and offers Create one. Once you pick a playbook, the size list becomes one button naming it; its menu offers Sketch, Task and Epic again, then the other playbooks. Under a playbook, Model is labelled Max model: the highest level any of its stages may use.

A playbook can't be changed once the task is saved: its name shows on a locked button, and hovering it says Playbook is fixed after save.

Involvement​

PickMeans
UnattendedThe runner decides everything itself.
GuidedThe runner asks you before key decisions.
InteractiveAsks like Guided. When the work is done, the runner uploads its report (a code task opens its pull request as a draft) and asks you to pick Finish or Request changes. With Request changes and a Note, it revises the latest result and asks again. Finish ships it as usual: the pull request leaves draft and merges, and a sketch settles.

An epic offers Unattended and Guided only.

When your organization's plan includes intelligent routing and the project's Routing mode is Recommend, a Recommended box above Advanced shows the runner the router would pick for a Coder task: its Runner, Tier, Model and Review, and why. Use this sets the Agent to it; the box then reads Accepted, or Overridden if you pick another. Exploring marks a pick the router is trying out. See the Routing setting in Projects.

Advanced​

Advanced open: Persona Coder (default), Agent Default, Model Inherit, Account Any, Priority Normal, and Depends on with Add a prerequisite

SettingWhat it does
PersonaThe kind of expert that runs the task. Only some personas open pull requests: a Researcher, for one, hands back a report. Starts as the project's Default persona, else your organization's default (Coder unless changed). Changing it leaves the size list as it is. Not shown for an epic or a multi-stage playbook.
AgentWhich engine runs the task. Default uses the project's Default agent, if it has one. Built-in lists Jaah's own runners; Your agents & catalog lists your organization's agents and the catalog connectors it turned on. Engines other than Claude, and your agents, appear only when your organization's plan includes them. An agent that can't run this persona is greyed out with the reason. See How agents work. Not shown for an epic.
ModelThe model level. Inherit uses the task's default, then the project's. Org Owners and Admins only. Not shown for an epic.
AccountThe model account the task runs on. Any lets Jaah pick. Lists your organization's enabled accounts, narrowed to the agent's vendor when you picked one. Not shown for an epic, or beside one of your agents.
NodeThe node the task runs on, from the ones the project runs on. Any takes a free one. Shown only when the organization's Node picker is on; see Settings. Not shown for an epic.
PriorityHow soon it runs compared with other tasks: Urgent, High, Normal (the default) or Low. An epic's sub-tasks take its priority, and changing it later changes every sub-task that isn't finished.
ThrottleShown for an epic only. How many of its subtasks may run at once: No (no limit), a number from your organization's agents down to 1 (10 when the plan has no agent cap), or Manual, where each subtask waits as Held until you press Run. Lowering it on a running epic applies at once: the most recently started subtasks stop and queue, and resume where they stopped when a place frees. Run on a subtask still waits for its prerequisites and the throttle.
Depends onTasks that must finish first. Type a task number, title or task link in Add a prerequisite; a number or link also finds a finished task.

Advanced on an epic: Priority Normal and Throttle No, then Depends on

When a task you file finishes, its assignee and you are told, and the board marks it until each opens it. Whether the runner draws on project memory is the project's setting, not the task's; see How projects work.

Hover a setting's label, such as Persona or Model, for a one-line reminder of what it does; where there's more to say, More opens the rest. What each persona does is in Personas.

The buttons​

ButtonWhat it does
DiscardLeaves without creating the task. Once you've typed something, Discard changes asks you to confirm: Discard or Keep editing.
SaveSaves the task as a Draft, to start later.
GoSaves the task and starts it. Ctrl+Enter (⌘+Enter on a Mac) does the same; hover Go to see it. Not shown if you can't start tasks in this project.

Save and Go close the form and return to the board, with the new task shown: Save on the first stage (Ideas), Go on the build stage (Building). If an attachment or a prerequisite couldn't be saved, the task is still created and the button reads Retry upload or Retry prerequisites (with and start after a Go).

Save and Go stay unavailable until the description has text, and until a project is picked: hover Save to see Pick a project. Go is also unavailable, with the reason on its hover, when nothing can run tasks in the project yet, such as when it has no model account, or while your organization awaits approval. Save still works then.

While you type, Jaah saves your work every few seconds, so a closed tab doesn't lose it. The task stays off other people's boards until you select Save or Go. Once that happens, Discard keeps the task: its confirmation says the task is already created and stays on the list, and Stay here keeps you on the form.