Skip to main content

Task page

Every task has a page of its own. It shows what the task was asked to do, what it produced, what happened along the way, and the actions its state allows.

Select a task's title on the task board to open its page beside the board. Select ⤢ at its top right for more room, or ✕ to close it. A link to a task opens the same page. While it is open, the browser tab is named after the task, such as Jaah | Fix the login timeout.

To act on a task from here, see Stop, restart or reset a task and Read a task's result. For the states and what moves a task between them, see How tasks work.

The header​

The task page of a Done task on its Task tab: the project and title, the Live Cast camera, the Done check and ⋯; the tabs Task, Artifacts, Comments, Routing and Details with the rating stars; the description, the size and involvement lists, Attach, Assigned to, From issue, Advanced, Origin task or PR, and Close, Save and Go

At the top, on one line, are where the task is filed, such as acme / Billing, and its title. The title is cut short when it doesn't fit; hover it, or select it to edit, for all of it. The task's number is on the Task tab. Select where it's filed for a Search box over your projects and their features, and pick one to file it somewhere else: see File a task under a feature. On a tablet, Back before them returns to the page you came from. Beside them, each only when it applies:

ItemWhat it shows
CameraThe task's Live Cast setting.
Where the change runsOnce the task's change merged, how far it got, marked ↗: On dev, Releasing, Released or Live (on an epic of a hosted app, Live or Setting up). Select it to open the app at that stage's address in a new tab.
⚠ IncidentThe task was filed for a Production QA incident. Select it to open the incident. Shown only when your organization's plan includes Production QA.
IssueThe tracker issue the task is linked to, its tracker and key, such as Jira PROJ-12 ↗. Select it to open the issue in a new tab.
OrgOn a task of an organization other than the one you're in: that organization's name. Not on a phone.
Accept, DiscardOn a draft Suggested by Jaah.
State iconThe task's state as an icon, such as ✓ for done; hover it for the word. On a draft or paused task, select it to start the task; on a task that holds a runner, it opens the console. On a queued task that can't start yet, hover or tap it for why, such as no free runner or an offline node, and what to do. An epic none of whose subtasks can run shows its first held subtask's reason. On a phone it sits on the Task tab instead, and is hidden while the task asks a question: Q&A is marked then. Why a queued task waits is then the first line of the ⋯ menu.
ReconnectOn a queued task held by something you can fix yourself, such as your own revoked Git sign-in. Opens where to fix it.
Start fresh elsewhereOn a task whose last MicroVM a node still holds: starts it on another node.
Console buttonOpens the web console of a task that holds a runner. On a phone, use Console in the ⋯ menu.
⋯The task's menu. See The ⋯ menu.

A banner under the header says why a task isn't moving, when there's a reason to show:

BannerShown when
The failure reasonThe task failed. It says why; the runner's longer account, such as an error log, is folded under Details.
Your answer not picked upThe runner hasn't picked up your answer, on a task with no Q&A tab. The same warning as under Q&A, with Console, Stop and Reset when you can run the task.
PausedThe task was paused for a reason outside it. The banner says whether it resumes by itself.

Live Cast​

On a task in a project whose Live Cast is on, an org owner or admin sees a camera button in the header: plain for Published, struck through for Hidden, dimmed for Pending until the rules check the task. Tinted means an override (Manual), plain the rules' verdict (Auto); hover it for both words. Select it to pick Published, Hidden or Auto (back to the rules). Attachments and artifacts follow their task. Shown only when your organization's plan includes Live Cast.

Tabs​

TabWhat it shows
TaskNamed with the task's number, such as Task 42. The description and the task's settings, the same form you start a task with. Changes save as you make them; Save saves now, Go saves and starts, and Close leaves. See Task.
SubtasksThe task's subtasks. Shown only when it has some, as an epic does. See Subtasks.
ArtifactsFiles the task produced, such as its report. Shown only once it has one. See Artifacts.
Q&AThe task's questions and their answers. Shown once it has asked something. A task that's asking opens here. See Q&A.
CommentsThe task's discussion, with the count once there are comments. See Comments.
AgentThe live event stream of the task's agent session. Shown once it has one.
RoutingWhat the agent router chose for each run of the task, and why. Shown only when your organization's plan includes intelligent routing. See Routing.
DetailsEverything about the run: Summary, Outcome, Metrics, Timeline, Versions and Review, each shown only when it has something to show. See Details.

The stars beside the tabs rate a finished task, from one to five: a top-level task or an epic, never a subtask. Select a star to give yours; it counts at once. Until you vote, the average of other people's votes shows beside the stars. Once you vote, the stars fold into the average with a star, such as 4.5★: hover it for 4.5 out of 5 — 2 ratings and each person's vote, and select it to open the stars again and change yours. A vote can be changed, not taken back. When the tab strip is too narrow, the stars move to the Task tab as Rating, and the header shows the average with a star. See Rate a task's result.

Task​

Priority is under Advanced, as in New task. On a top-level task you created, Advanced also has Hidden: it keeps the task and its subtasks off the board unless the board's Hidden filter is on. A hidden task asking a question still shows. Below the form, when they apply:

FieldWhat it does
Origin task or PRThe task number (#123) or pull request URL whose merged work caused what this task fixes. Shown when you can decide outcomes.
RatingShown here when the tab strip is too narrow. A vote counts at once.

Origin task or PR applies when you select Save or Go, never as you type. So does moving an epic that has subtasks to Task in the size list: a warning says that saving stops its subtasks and archives them, and only the title and description save as you type until then.

Subtasks​

An epic's Subtasks tab: Prepare with Analyze, Design and Plan, then Phase 1 — Core with its build subtask, then Finish, each subtask done

An epic's subtasks are grouped by stage:

GroupHolds
PrepareThe analysis stages: Analyze pins down the requirements, Design chooses the approach and Plan splits the work. The epic a new web app starts with opens with App Wizard, which asks you about the app first.
BuildThe subtasks that build the work, one group per phase of the plan, such as Phase 1 — Core. Unphased holds build subtasks with no phase.
FinishThe stage that checks the result as a whole.
Blind reviewThe advisory reviews of a build subtask: reviewer, security reviewer and tester.
OtherAny other subtask.

Each group shows how many subtasks it holds. Select ▾ beside its name to fold it, and ▸ to open it again. Each subtask is drawn like a row on the task board: its state, number, title, creator and age. Select its title to open it. The tab only shows subtasks; act on one from its own page.

Artifacts​

The Artifacts tab: report.html marked Report and Current, with its size, age, a download button and ⋯, and the report previewed below with its size, region and a Download button

Each row is one file: its name, its kind (such as Report), its size and age. Current marks the newest file of each kind. The tab opens on the current report, or on the newest file when there is no report; a file added after the report doesn't take its place. Select a row to preview it below the list, under a line with its kind, name, size and the region where it's stored, such as Region: US East (N. Virginia). Audio and video (such as MP3 and MP4) play in place. Select Download, or the download button on its row, to save it. A file that can't be previewed in the browser shows only Download.

Older versions of a report are folded under the current one, whose row counts them, such as 16 earlier versions. Show earlier versions in the row's ⋯ menu lists them, and Hide earlier versions folds them again. Versions are numbered, v1 being the oldest; so are files uploaded again under one name. With a row focused, press ↑ or ↓ to preview the next one.

A long list scrolls on its own so the preview stays in view; +10 more at its foot counts the rows below. Drag the line under the list to make it taller or shorter; double-click it to reset. The browser remembers the height.

If a file can't be loaded, select Retry.

Q&A​

While the task is asking, its open questions come first, under Questions, then History: the questions already settled. With several questions, 1 of 3 says where you are, Back and Next move between them, and Send on the last sends every answer; 2 unanswered marks the ones you skipped and goes back to the first. Someone who can only view the task sees the questions without the answer controls.

Under the options, Note (or Answer when the question has no options) is the same box as a comment: the formatting bar, @ to mention someone, who is then notified, and the paperclip, paste or drop to add screenshots and other files. They're sent to the runner with your answer. Picks, notes and files you have not sent yet are kept for you until you send them, even if you close the task. Picking an option sends it after a moment, except Request changes (or any option that asks for changes): it waits and puts the cursor in Note, so you can type what should change and then select Send. See Answer a task's question.

When a task that has files under Artifacts asks, Open artifacts sits beside the button that copies all questions, above the open ones. It opens an Artifacts pane beside the page, in the console's place, with the current report shown (the newest file when there is no report); drag its edge to resize it and select ✕ to close it. When a running task asks a question and has added a file since its run started or since its last question, the pane opens by itself, once per question. On a phone the pane never opens: the button switches to the Artifacts tab instead.

Once nothing is open, the tab lists every question the task asked and its answer, newest first, each answer after the name of the person who gave it, such as Ann Lee:. A typed answer or note keeps its formatting, and its screenshots show as thumbnails that open full screen. Revise on an answer asks the question again. Someone who answers in the task's console, in the runner's own terminal, sets the task going again just as an answer sent here does. The tab can't tell who typed it, so that answer reads Terminal:; hover or tap it for its details, which say Answered in the terminal.

Whether your answer reached the runner shows here too. If the runner hasn't picked it up after a while, a warning says so, with Console, Stop and Reset when you can run the task.

Comments​

The Comments tab: No comments yet., then the Comment box with Bold, Italic, H2, • List, ☑ Checklist, 🔗 Link and ⋯ above it, and the paperclip and Send under it

Comments run oldest first, with the box at the bottom. Each shows its author's initials and name (on a phone, the initials alone), how long ago it was posted, and edited once changed; hover the age for the exact time. A comment keeps its formatting and line breaks. Its pictures show as thumbnails under the text, and selecting one opens it full screen; the Escape key, its close button or a click anywhere closes it. Ctrl-click (⌘-click on a Mac) or a middle click opens the picture in a new tab instead. Any other file is a chip with its name that downloads it.

ItemWhat it does
Formatting barThe same bar as the task's description: Bold, Italic, H1, H2, • List, 1. List, ☑ Checklist, a quote, Code, a code block and 🔗 Link. When the box is narrow, the less used ones move under ⋯.
Comment boxType a comment. Enter starts a new line. Misspelled words are marked as you type, except in code. Type @ to mention someone: pick a name from the list, and that person is notified. Paste or drop files into the box to attach them.
@Mention someone: types @ in the box and opens the list of names. Shown when there is someone to mention.
PaperclipAttach files: adds files of any kind. Each shows above the buttons, a picture as a thumbnail and any other file by its name, with × to take it off before you send.
SendPosts the comment. Ctrl+Enter (⌘+Enter on a Mac) does the same. A comment can be files alone.
Reply (↩)Under another member's comment: puts @ and their name at the start of the box, so your reply mentions them.
Add reaction (☺)Adds an emoji reaction to a comment. Select a reaction again to remove yours; hover one for who reacted.
Edit, DeleteChange or remove a comment you posted. Edit opens it in place, with Cancel and Save; the Escape key cancels. Delete comment? asks you to confirm.

The actions sit on the line under each comment.

How to use them is in Comment on a task and Format a comment and attach files.

Routing​

The Routing tab of a task the router never handled: No routing decision yet

What the agent router decided for each run of the task, one card per attempt: whether it is the Next dispatch, Dispatching or Dispatched, the reason in words, and its Mode, Router's pick, Review, Default and what it Ran on. Candidates lists every runner it weighed, Eligible or Excluded and why. While a recommendation waits, Use this takes it; on a pick the router made by itself, Change opens the Task tab to pick another. Review lanes used names the review agents the task's runs reported. A task with no decision yet shows No routing decision yet, or the blind-review line when there is one. How a project routes is set under Routing in its Settings › General.

Details​

Details has a tab for each record of the run. Summary is always there; the others show once they have something to show.

Summary​

A done task Jaah couldn't confirm as a success opens with an Unverified — warning that says why. When the task never asked you anything, a note may say why.

The Summary tab: State with Change…, Language with Change…, Parent, Created, Updated, Created by, Updated by, Source, Runner with Sessions and Project memory, then Outcome with the runner's summary, closed with no PR — no code needed and its evidence, and Compliance manifest Sealed v1

ItemMeaning
TagsThe task's tags. Re-tag classifies it again from its description and outcome; Re-tag this task? asks first when that would replace tags set by hand. Tags come from the tag groups published in Settings.
State · Change…Changes the task's state by hand; the state itself is the icon at the top. Shown only if you can run the task.
LanguageThe language the task is written in, such as English. Change… picks another; it applies to the task's subtasks too. A subtask shows its epic's. See Set a task's language.
ParentThe epic this task belongs to, or —.
Created, UpdatedWhen it was created and last changed.
Created by, Updated byWho did it. System means Jaah itself.
SourceWhere the task came from, such as Console, Schedule or Slack. A task an automation filed shows Automation · and its name; an org admin can select the name to open it. If the run cost more than the trigger's budget, a warning shows its cost against that budget.
From templateThe template the task was started from. Select it to find the template in the gallery; once the template is deleted, its name shows as plain text. Shown only for a task started from a template.
RunnerWhether a runner is working on it now; once it finished, where it last ran. Sessions opens its runs.
Project memoryWhether the task drew on project memory, and how: for example On (default) · 5 injected · 2 read · 1 cited. Shown once the task has run.
OutcomeThe runner's own summary of what it did, and every pull request the task opened, one per repository, such as acme/api #7, each with its state: open, merged or closed. Pull requests show while the task still runs. A task from before this list shows one merged PR ↗ link instead. A task that ended without a pull request says closed with no PR and why, such as no code needed, with the runner's Evidence under it; one closed with Complete says closed by hand, with the outcome given there as its summary; one whose pull request was left open for your team to merge says handed over — PR left open for your team. For a project with no repository there's nothing to merge: Report opens the task's report on the Artifacts tab.
Merge gatesThe gates of the newest merge lane run that tested the task's pull request, one row each. Shown once such a run has results.
Merge-lane stagesEach merge lane run that held the task's pull requests, newest first: every stage, how long it took, and Failed or Flaked (passed on a retry) when it didn't pass cleanly. Shown only when your organization's plan includes Production QA.
Compliance manifestA signed record of how the task was built, sealed once it's done. See Compliance manifest.
Finisher notesNotes from the stage that wrapped up an epic, including every pull request its subtasks opened. Reads No finisher notes yet. until there are some.
BlocksTasks waiting on this one, or Nothing depends on this task. One marked stale may need to run again: hover the mark for why. Re-run starts it again.
Compliance manifest​

The section shows where the task's manifest stands:

ShownMeaning
Seals when the task is done.The task hasn't finished yet.
A reason, with GenerateNo manifest was sealed, for example because the task finished before manifests existed. Generate seals one now.
Sealing…The manifest is being signed and stored.
Sealing failedIt couldn't be sealed, with the reason. Regenerate tries again.
Sealed v1 and its timeThe current version. HTML downloads a readable copy and JSON the signed file. Regenerate seals a new version.

Earlier versions lists the versions before the current one, each with its own downloads. When the task gained newer data after sealing, a line says so and Regenerate includes it. Generating or regenerating needs edit access to the task; anyone who can view it can download.

Verify a manifest opens Verify a compliance manifest, which checks that a downloaded file is one Jaah signed and that nothing in it changed.

Outcome​

The Outcome tab: Dispatch 1 with Settled and Backfilled, the chips Agent, Auth, Persona, Review and Node, then the Timeline and Gate figures

What happened to each run of the task after it ended: whether its change merged, deployed and lasted, or was reverted or fixed forward, with any defect traced to it. One card per run, numbered from Dispatch 1. Shown once the task has one. The runner's own account of the run and its pull requests are the Outcome field on Summary; cost, tokens and model are on Metrics.

The chip after the heading is where the run ended up; hover it for the words:

ChipMeans
PendingNot merged yet.
Merged, ReleasedMerged (and released); the time it must last without a defect is still running.
SurvivedMerged and lasted that time with no defect.
RevertedA later commit undid the merge.
Fixed forwardA later change fixed a defect this merge caused.
Incident linkedA production incident was traced to this merge.
Failed, AbandonedThe run ended without merging.
SettledFinished with nothing to merge, such as a report.

A dashed Backfilled, with an info mark, marks a card recorded from history after the release, with only its merge, lane and cost facts; hover it to read so. Shadow marks a benchmark run beside the real one, never merged; Excluded, a run left out of every figure, with the reason on hover.

PartShows
ChipsAgent, Auth (how the run signed in to its model account, such as Subscription), Persona, Review and Node. — means not known. Node names the node and its kind, or reads Not recorded.
TimelineWhen the run was Ready, Dispatched, First active, PR opened, Enqueued, Merged, Released and Ended, and when Survival ends.
GateLane failures, Pushes after enqueue, Non-runner commits (commits the runner did not make), Security findings, Lane time, Node time, the Diff (lines added and removed, and files changed) and the Merge commit.
Defect linksLater changes or incidents traced to this run, each with how sure Jaah is (High, Medium or Low; hover for the figure). Someone who can decide outcomes sees Confirm and Dismiss on a proposed link.
Benchmark duelOn a task run twice to compare two setups: both setups, the shadow run's pull request, the gate, how far the two changes differ and the Result.

To charge a defect to the work that caused it, use Origin task or PR on the Task tab.

Metrics​

The Metrics tab's Task run metrics: Total run time, Agentic time, Tokens in / out, Token cost estimate, Peak RAM, Peak CPU, CPU time and Model

Task run metrics shows the run's figures. While a runner works, they update as you watch.

ItemMeaning
Total run timeHow long the task ran.
Agentic timeThe time the agent was actually working.
Tokens in / outHow much text the model read and wrote.
Token cost estimateWhat those tokens cost at the list prices in force when they were used. A later price change does not alter it.
Peak RAM, Peak CPUThe most memory and processor the run used at once; 100% is one full core.
CPU timeThe processor time the run used.
ModelThe model level the task ran at, and the model it used. Shown when known.

Peak RAM, Peak CPU and CPU time show once the node reports any of them; a missing one reads not reported.

Timeline and Versions​

The Timeline tab: Created, Run, Runner session attached, Runner started, Outcome reported, Runner ended (done), and Notification, each with its time

  • Timeline — every step, oldest first, with its time and the state it moved to. A step a person caused names them after the time; a step Jaah took names no one. Each step is one line: hover it for the whole text, or select it to open its details, such as the session, node and changed fields. A changed description says Description changed; Versions shows it. While a runner works, its Runner started step shows how long it has run, and the time keeps counting while you watch. A message the runner's agent wrote is its own step, headed by the agent's name. A notice Jaah typed into the runner's session, such as merge lane news, is a Control-plane notice step. When a runner ends early, its step shows the reason it gave.
  • Versions — earlier versions of the description. Compare on a version shows what the next edit changed in it.

Review​

What the review checks found in the task's change, most severe first: each finding's severity, kind, file and line, what's wrong, which check found it and which agent wrote the change. Findings are advice; none blocks the task. Shown once there's one.

The ⋯ menu​

The ⋯ menu of a Done task: Edit, Duplicate, Pin, Start, Reset, Delete and Re-generate title

The menu offers only what the task's state allows, so it varies:

ItemWhat it does
Act as organizationOn another organization's task: switches this tab to act as that organization.
EditOpens the Task tab, where you change the task. Shown if you can change the task. See Edit a task.
DuplicateOpens a new task filled in from this one. On another organization's task it reads Duplicate as organization, and the copy goes there.
Pin or UnpinPin keeps the task at the top of its section on your board; Unpin returns it to its place. Your pins are yours alone. Not on subtasks. See Pinned tasks.
StartQueues the task for a runner. On a finished task, it runs it again. On the task's page, Start then returns you to the board's build stage. When your git account can't see the project's repository, it asks You can’t see this repository first, with Don’t ask again: see Start a task when you can't see its repository.
StopStops the runner. The task is paused.
ConsoleOpens the live session of a running task.
StackOpens the running app the task is working on.
ResetEnds any run and puts the task back to Draft, so you can change it and start again. Its questions and answers, reports and activity are kept unless you tick Delete artifacts in the confirm. On an epic, its subtasks are reset too, and Start runs it from the top.
CompleteMarks the task done, after a confirm. Outcome (optional) takes one line, up to 200 characters, that the board shows on the task's hover and the Outcome field on Summary shows. It starts with the runner's own summary, else your last answer to the task's questions.
DeleteDeletes the task, its subtasks and attachments for good, after a confirm, in any state. A running task is stopped first. Tasks that waited on it wait on what it waited on.
Re-generate titleWrites a new title from the task's current description, replacing the old one. On the task's page only, if you can change its title.

The Reset confirm: Reset “task title” to draft? A live runner is killed. Its questions and answers, reports and activity are kept unless you tick the box. Then Delete artifacts, Cancel and Reset

Changing a task's run needs edit access to its project. Without it, those items aren't shown. What each state means is in Task board.