Skip to main content

Task board

A task is one piece of work you hand to Jaah: you describe it, a runner does it, and the result comes back to the task. The task board lists your organization's tasks. It's the page Jaah opens after you sign in.

To create a task, see Start a task. To reply when a task asks you something, see Answer a task's question. To stop, restart or reset one, see Stop, restart or reset a task. For the ideas behind tasks and their states, see How tasks work.

The board​

A slim strip of tabs leads the board's top line, beside search and the view's buttons:

TabShownWhat it holds
TasksAlways; the defaultEvery task in one list.
PipelineWhile a project is picked in the sidebar's Projects treeThat project's tasks by stage. See The pipeline.
SchedulesTo an organization owner or admin; to a project's Maintainer while that project is pickedThe automations of the picked project, or of the whole organization when no project is picked. The list is the Automations list; its search and filters sit on the tab strip, beside the tabs.
SettingsWhile a project is pickedThe picked project's settings, the same sections as on its page. See Projects › Settings.

Each tab is a link: the board's address names the tab, so a copied link opens the same one. Going back to the board, such as with Save on a task, opens the tab you last showed in this browser tab. Pipeline also remembers the stage you picked for each project. A tab the current pick doesn't offer opens Tasks instead. The project picked in the sidebar stays highlighted on every tab. See Switch between the tasks and pipeline views.

Select a project or a feature in the sidebar to see only its tasks. All projects shows every task you can see, except those in projects and features you hid. See Hide.

The browser tab is named after what you are looking at: the picked project or feature and the view, such as Jaah | Mobile app tasks or Jaah | Mobile app pipeline; with All projects, the tab you are on, such as Jaah | Tasks. With a task open beside the board, the tab carries the task's title instead.

The board's top line: the Tasks and Schedules tabs, Search tasks, the assignees' initials (blurred here), then the Focus button (a pulse icon), the Filter & view button (three sliders), and the blue New task button with its ▾ menu

The toolbar runs left to right. The two square buttons before New task carry icons, not words; hover either for its name.

ControlWhat it does
Search tasksFinds a task by its number, or by a word in its title or description.
InitialsOne badge per person assigned a task you can see, you first. Select one or more to show only their tasks; select again to clear. After three badges, +2 (the number left) lists the rest, with a box to find a name.
Focus (the pulse icon)Hover text: Focus — hide finished tasks and queued subtasks. Hides finished and archived tasks, and queued subtasks, so the work left to act on stands out. The button stays highlighted while Focus is on; select it again to show them. The board remembers your choice.
Filter & view (the sliders icon)Hover text: Period, assignee, creator, source, hidden and grouping. Opens Filter & view. A number on it counts the filters that are on.
New taskOpens a new task. See New task. On a phone it's +.
▾Opens the menu below. Without permission to create tasks, it stands alone and reads New ▾.

The New menu: Task and From template

  • Task: a new task. Same as New task.
  • From template: opens the template gallery, where Start or Customize files a task from a template. See How templates work.

Under the toolbar, the row New task… creates a task in one line. Before it, a project button such as Invoicing ▾ names the project the task goes into; select it to pick another. Beside its ▶ button (hover text: Create this task and start it) the row shows the mode the task starts in, Unattended or Guided. ▶ or Enter creates the task and starts it. ⤢ (or a double-click on the row) opens the full editor. See Start a task.

If you can't create tasks, the board has no New task, no Task or From template item and no one-line row.

On a phone​

The phone header: the Tasks and Schedules tabs, and under them one line: All projects, the search, Focus and Filter & view buttons, and the blue + button with its ▾

On a phone, the header is one line. It starts with what the board is scoped to, such as All projects; select it to pick a project or feature. Then come search, Focus, Filter & view and +. Select search to open Search tasks under the line; select it again to close the box and clear the search. On a project's board, the New task… row has no project button: the task goes into that project. A queued task held back says why when you hover its status icon or its title, such as Waiting. Organization runner limit (1/1) or Waiting. 2 prerequisites; on a phone, tap its status icon. An epic none of whose subtasks can run shows its first held subtask's reason the same way, such as Waiting. Subtask #5940: node disk full; resumes under 75%. A prerequisite that is done but whose PR is still in the merge lane still blocks: it shows merging under Depends on.

Sections​

By default, tasks are grouped by state. The sections below are the state grouping:

SectionHolds
QuestionsTasks asking you a question.
StoppedTasks that stopped: a failure, a pause, or no balance left to run on.
In progressTasks starting or running, and an answer on its way to its runner.
QueuedTasks started and waiting for a runner.
DraftTasks saved but not started: yours, ones assigned to you, and ones no person filed. Other people's drafts still open from their links.
Suggested by JaahDrafts a runner filed on its own while working another task. See Suggested by Jaah.
DoneFinished tasks. Folded away at first: select ▸ beside it to open it. This browser tab remembers your choice; a new tab starts with Done folded again. Under Tasks, grouped any other way (by project, say), each group's finished tasks fold under a ✓ Done row at the group's end, remembered the same way. Done opens with each project's Next release under a blue truck: its finished tasks still waiting to ship, including those whose pull request the merge lane is still merging. Next comes any release on its way, with the tasks it carries. Then the tasks a release shipped fold under that release: a green truck, the release's version in bold (New version until it has one) and the stage it reached in green, such as v1.8.2 Production. See Release rows. Releases and the tasks no release shipped are listed newest first. The icon after the heading, Show as list, drops the release rows and lists the finished tasks alone, newest first; Group by release brings the release rows back. Grouped any other way, the same icon sits after each group's heading. This browser tab remembers the choice. See Find what shipped in a release.

Each header shows how many tasks the section holds. Stopped adds its make-up beside the count, such as 2 failed, 1 paused. When Jaah holds queued tasks back, Queued says so: its header becomes the reason when every queued task waits for the same one, such as Waiting · GitHub sign-in revoked for Ann Lee, or adds 2 waiting beside the count otherwise. When the reason is one you can fix, such as a revoked sign-in, Reconnect at the header's right end opens where to fix it. A section with no task is left out.

Group by in Filter & view swaps these sections for others. Hover an option there for a reminder of what it makes:

Group bySections
StateThe sections above. The default.
FeatureOne section per feature, then one per project for the tasks in no feature.
RecencyRunning now, Last hour, Today, This week and Older, by when each task last changed. With Focus on, queued tasks sit in a last Queued section.
ProjectOne section per project. Under All projects only.
A tag groupOne section per tag of that group, in your tag order, so a finished section can sit above a running one.
NoneOne list, unfinished tasks first.

A section's heading starts at the left edge. Under Project or a tag group, select a group's heading to fold it, and again to open it. A folded group's tasks can't be ticked.

Automatic​

Tasks grouped by project: under Mobile app, a closed Automatic 2 row with a gear, then a closed Done 1 row

Work a schedule, a trigger or an agent filed on its own folds under one Automatic row with a gear, at the end of each list: a section's open work, and a group's ✓ Done row. The row shows how many tasks it holds and starts closed. Select ▸ to list them, and ▾ to fold them again. A link to one of its tasks opens it.

What needs a person stays a row of its own: a task asking a question, a failed task, and a draft Suggested by Jaah. A tracker issue, such as one from Jira or Linear, never folds: it is a person's assigned work. When Source in Filter & view is set to automatic sources only, without Console, nothing folds.

A board with no task at all says No activity. Select a task's title to open it beside the board. What the task page shows is in Task page.

Each row shows:

A section whose header names its hold reason (blurred here, as it names a person), with its Automatic 8 row open: each row's status icon, title, persona such as Translate, creator → assignee (blurred here), project, age and ⋯

ItemMeaning
CheckboxTakes a done task's status icon while you hover the row, and stays on a ticked row. Tick rows to act on them together. See Select several tasks.
Status iconThe task's state. On an epic, a ring around it fills as its subtasks finish. Hover it for the state, then the facts behind it: the reason a failed or paused task stopped, or where a running task runs. Select it to act: ? opens the question, ▶ on a draft or paused task starts it, and a running task's opens its console. A pulsing ring around ✓ marks a finished task you haven't opened yet; it stops once you open the task, or once the task has been finished longer than your organization allows (7 days unless an org admin changes it; see Set how long finished tasks glow as unread). On a running task, a click anywhere else on the row opens its console too. See States.
NumberThe task's number, in the ID column. Hidden until you turn ID on under Columns. Search finds a task by its number either way. Select it to copy the link to the task; the number flashes green once it's copied. See Copy a task's link.
TitleGenerated from the description when you don't give one. Grey when a schedule, trigger, agent or the system filed the task, so people's tasks stand out. Select it to open the task. On a finished task, hovering the title or the status icon also shows its one-line outcome, such as the one given with Complete; on a phone, tap the status icon. Hover the row for a copy icon beside the title, Copy link, which copies the link to the task.
▸ before the titleThe task has subtasks. Select ▸ to show them, and ▾ to fold them again. Expand subtasks in the row's ⋯ menu does the same.
📌 after the titleYou pinned the task. Select 📌 to unpin it. See Pinned tasks.
Priority after the titleA queued task whose priority isn't Normal: ⇈ Urgent, ↑ High or ↓ Low. On a narrow board only the arrow shows.
⚙ or 🗄 after the title⚙ marks a hidden task, such as system bookkeeping; 🗄 an archived one. See Hidden in Filter & view.
Gates and wall timeOn a merge lane task, the gates its run ran and how long it has taken, such as 9 gates · 72m; a running one keeps counting. Slow marks a run past twice the project's last full gate.
PersonaThe kind of expert that runs it, such as Coder, Researcher or Epic. Every row names one. On a top-level task, the project's default persona is dimmed, so a task with another persona stands out.
RatingA finished task's average rating out of 5, with a star. Shown once someone has rated it on its task page. Hover for how many ratings it has.
TokensHow many tokens the task and its subtasks have used, such as 483.5K. Hover for the exact count; a running task's figure updates every few minutes. Hidden on narrow screens.
CostWhat the task's runs have cost so far: whole dollars rounded up from $1, cents below, such as $13 or $0.66. * after it means the figure includes a cost the agent reported itself. Hover for the exact figure. Hidden on narrow screens.
Creator → AssigneeWho created it and who it's assigned to, as initials, such as RZ→JS. A task filed by a schedule (⏱), a trigger (⚡), an agent (✦) or the system (⚙) shows that mark instead of the creator; hover it for the name. A task you assigned to yourself shows your initials once. If you can edit the task, select the assignee to pick another project member. See Reassign a task.
ProjectUnder All projects, the project the task is in. Not shown when the board is grouped by project.
AgeHow long ago it last changed.
⋯The same menu as on the task page. See The ⋯ menu.

A top-level row dragged onto a feature or project in the sidebar is filed there. See Arrange features in the sidebar.

When your git account can't see a project's repository, Start (from a row, Accept or the New task… row) first asks You can’t see this repository, with Fix access when the forge names where to grant it. Run without repository starts the task in an empty folder, without the code. Tick Don’t ask again to start that project's tasks without the repository from then on without the question; it comes back once your account can see the repository. See Start a task when you can't see its repository.

When no runner slot is free and stopping a running task would make room, Start first asks No capacity for “…”, with why it can't start and the running tasks to pick from. Stop & force-start stops the one you picked and starts this task in its place; Just queue it starts it to wait its turn. See Start a task when no slot is free.

A few notes can sit above the list. Showing the first 500 tasks — some may be hidden. Pick a project to narrow the list. means more tasks match than the board loads at once. A link to a task that's gone says Task 123 no longer exists — it may have been deleted., with Dismiss. When a link opens a task beyond the loaded list, the task (or, for a subtask, its epic) is pinned to the top with Task #123 is outside the loaded list — pinned to the top.

Release rows​

Done grouped by state: two Next release rows under a blue truck, each with its count, tokens, cost, project and age, then finished tasks

The Tasks view's Done and the Pipeline view's release stage draw a release the same way, as one row among the tasks:

ItemMeaning
TruckGreen for a release that shipped; blue, on a plain disc, for the Next release. A release on its way shows a purple truck in a turning ring while it runs (Releasing), an amber truck while it waits for approval, and a clock while it is scheduled. Hover it for the word.
NameThe release's version in bold, New version until it has one, or Next release. Select it to list what it holds, and again to fold it.
StageThe stage the release reached, in green, such as Production.
CountHow many changes it holds. Hover for the words.
Run statusOnly when its deploy run failed or is still running, such as where it failed.
Tokens, CostWhat its changes used and cost, in the same columns as a task's.
ProjectUnder All projects, the project it belongs to.
AgeHow long ago it shipped; on the Next release, the age of the oldest change waiting. Hover for the date.
⋯Open run opens its deploy run. Shown only when your organization's plan includes Production QA.

Open, a release lists its tasks by feature, each feature folded until you select it. A merged change with no task is a line of its own. Tasks a schedule, a trigger, an agent or the system filed sit in a folded Automatic row at the end.

Pinned tasks​

Pin a task to keep it at the top of the board: select Pin in its ⋯ menu, on the board or on its task page. A pinned task leads whatever section it falls in, whatever the Group by, and the rest keep their order. It stays pinned when it finishes or is archived. To unpin it, select 📌 beside its title, or Unpin in its ⋯ menu.

Your pins are yours alone: other members don't see them, and their pins don't move your board. Subtasks can't be pinned. You can pin up to 64 tasks; pinning another unpins your oldest.

Suggested by Jaah​

The Suggested by Jaah section: one draft, Timesheet cards overflow on narrow phone screens, with Accept and Discard beside its title, the age and ⋯

A runner that finds work outside its own task, such as a bug it ran into, can file it as a draft. Those drafts sit in their own section under Draft. Each one's description opens by naming the task it came from.

ControlWhat it does
AcceptStarts the draft: it joins Queued like any started task. Shown if you can start the task.
DiscardDeletes the draft at once, with no confirmation. Shown if you can delete the task.

The task page shows the same two buttons in its header.

Filter & view​

Filter & view: Period, Assignee, Creator, State, Source, Hidden, Group by and Columns

SettingWhat it does
PeriodShows only tasks that moved in a period: Today (since midnight), Recent (the past 7 days), Wider (the past 30 days) or Exact dates, which adds From and To dates. Any time shows all.
AssigneeShows the tasks assigned to some people. Anyone shows everyone's. Not shown when there's no one to choose between.
CreatorShows the tasks some people created. Tick one or more; System covers the tasks no person created. Each name shows how many tasks they created. Anyone shows everyone's. Not shown when there's no one to choose between.
StateShows only tasks in one state: Draft, Queued, Running, Asking, Failed, Paused or Done. Any shows every state.
SourceShows the tasks filed from some places only: Console, Schedule, Agent, Webhook, GitHub, Email, Slack, New user, Incident, Release failed, Health breach, Linear, Jira or Backlog. Tick one or more. Any shows them all.
ShowIn a project's Pipeline view only: Stages (the default), or its Not started, Done or Archived tasks, each with its count. See The pipeline.
HiddenAlso shows hidden tasks: system and archived ones, and for an Org Owner or Admin everyone's drafts. A hidden task asking a question is on the board even with this off.
Group byGroups the list by State (the default), Feature, Recency, Project, or a tag group. None turns grouping off. Project is offered under All projects only.
ColumnsPicks the columns the rows show: ID, Persona, Rating, Tokens, Cost, Creator → Assignee, Project (under All projects only) and Age. ID is off until you turn it on. The setting reads All while every column shows, else how many show, such as 7 of 8. Your choice is saved to your account, so it follows you to every device. On a narrow board, such as with a task open beside it, columns you left on still drop out to make room for titles: Persona first, then Tokens, Cost and Rating.

State lists Any, Draft, Queued, Running, Asking, Failed, Paused and Done

The button shows a count when a filter is hiding tasks, and a row of chips under the toolbar names each active filter, such as Search: “login”, State: Draft, Period: Today, Creator: System, Source: Slack or Hidden shown. Select a chip's × to clear that filter, or Clear all to clear them all. When the filters hide every task, the board says No tasks match these filters.

The chips row: State: Draft with its ×, then Clear all and ☑ Select all

A link from the command center opens the board already narrowed. Its window shows as a Period: chip with its two times, such as Period: Oct 29, 20:00 – Oct 30, 20:00 EDT, in place of the Period setting; picking a Period replaces it. A persona shows as a Persona: chip, such as Persona: Coder. Each clears with its × like any chip.

Chips from a command center link: Period: Oct 29, 20:00 – Oct 30, 20:00 EDT and Persona: Coder, each with its ×, then Clear all and ☑ Select all

Select several tasks​

Only drafts and finished tasks you can delete can be ticked, and not subtasks or archived tasks. Hover a done task and tick its checkbox, or, before you tick a row, select ☑ Select all in the chips row to tick every task the filters match, except tasks folded away under a closed Done, release or Automatic row. On a phone, press and hold a done task. Once the count is known the button reads Select all 3, or Select first 500 when more match than one selection can hold. A bar then sits under the list (on a phone, at the bottom of the screen) and shows how many are selected, such as 3 selected, with the actions that fit them:

ActionWhat it does
✕Clears the selection.
☑ Select all NTicks every task the filters match. Gone once all are ticked.
Delete NDeletes the selected drafts and finished tasks for good, with an epic's subtasks and every attachment, after a confirm.

The bar under the list with the one matching draft ticked: 1 selected, its ✕, and Delete 1

A row's ⋯ menu also has Select (or Deselect). Select a draft there: its status icon stays ▶.

When the list refreshes and a ticked task leaves it, a note above the bar says what is left, such as Kept 2 of 3 picks, or Selection cleared when none is.

Starters​

While your organization has 10 tasks or fewer, the unfiltered board shows a section under the list:

  • Set up, then start tasks: until the company setup is finished, one tile per setup step, left to right: its state, and a link such as Sign in or Projects on the step to do next. Org admins see it; other members see the templates instead.
  • Most popular templates: once setup is done, the templates started most, each with Start and Customize. All templates opens the gallery. Hidden while no template has been started.

Any filter, or more than 10 tasks, hides the section. See Start a task from a template.

The pipeline​

Select a project in the sidebar, then Pipeline at the top of the board, and a stage strip sits under the top line: one block per stage of the project's pipeline, with how many tasks are in it. By default the stages are Ideas, Building, Dev and Production. After the count, a red coin counts the stage's failed tasks and an amber one the tasks asking you a question; hover a coin for its words. Select a block to show only its tasks. A project you open from the sidebar opens on the stage that needs you most: questions first, then failures, then stopped tasks; otherwise the first stage. While someone has frozen the project, a Frozen now banner names who and since when.

A stage with an address shows a health dot: green Healthy, red Down, or a grey ring for Not checked yet. Hover it for where the check comes from and when it last ran.

The stage strip of a project: Ideas 1, Building 4, Dev 17 and Production 0, the Start, Merge and Release icons between them, and the gear at the end

Between two blocks, an icon in the step's colour marks the step that moves work on: Start, Merge, Start and merge, Move or Release; hover it for its name. Start and Move are followed by their counts as coins: failed (red) and waiting (grey). Select a waiting coin and the list opens with Waiting on and the step's chip. The Merge icon turns while the merge lane works, with the count in flight on its coin. Select a coin to show only those tasks. A step with work waiting ends with a chip naming why in a word or two, such as 1/2 approvals, Frozen, Soak 42m, Off hours, In line or Sign-off; hover or tap it for every reason, such as who may approve. The gear at the end of the strip opens the project's Settings › CI Pipeline, where the stages, who may do each step, approvals, whether a step runs by hand or by itself, and freezes are set: see Set up a project's pipeline.

Production's block shows the live version and how long ago it went live. A release's version is the project's own: the version tag on the released commit, such as 1.4.2. A project that tags no versions gets a release number instead, such as #12.

Under the strip, the list has one section per stage; with one stage selected, its tasks alone. Inside a stage, tasks are one list: questions first, then failed tasks, then stopped ones, then the rest, newest first. In the stage a release leaves from (Dev by default), a change the merge lane is still testing shows a flask in a turning ring as its status icon; hover it for Testing. Finished tasks filed by a schedule, a trigger, an agent or the system that merged a change sit in a folded Automatic row at the end of each stage, open by default on the first stage. A task whose pull request is merging is not in its stage: select the Merge step's turning coin to see it. The list loads 50 tasks at a time, and the next 50 as you reach its end.

Each stage's heading looks like a section heading under Tasks: its name and count. Select the name to fold the stage, and again to open it; folding a stage clears the tasks ticked in it. With one stage selected, the stage has no heading. The bar of ticked tasks sits under the list, in the same place as under Tasks, and offers what fits them, up to 1000 at once:

ActionWhat it does
Start N, Merge N or Move to stage NMoves the ticked tasks on through the step out of their stage. Shown if you may do that step.
Override freezeWhile a freeze holds the stage's Merge, to someone who may merge and edit the pipeline. Asks for a Reason, then merges them anyway; the override is recorded on the Audit page.
Approve N / Reject NOn a step that needs approvals, to those who may approve. Opens the step's instructions with an optional comment.
Archive NArchives the ticked tasks. Under Show › Archived, Restore N brings them back.
Delete N draftsDeletes the ticked drafts for good, after a confirm.

A finished task that changed no code, such as an answer, research or a design, moves on as a change does: once finished it sits in the stage after Merge (Dev by default) and ships in the next release. Finished tasks that sit in no stage, such as system tasks that changed no code, are in a folded ✓ Done row at the end of the first stage (Ideas by default), with how many there are; select ▸ to list them. Not started, Done and Archived tasks are also under Show in the filter menu, each with its count; Stages there goes back to the stages.

Production's section starts with a folded Next release row: what waits on the stage before. Then any release on its way, open, then the last release open and each older release folded. Each is a release row, as in the Tasks view's Done. Show as list at the right of the stage's heading lists the releases' tasks alone, newest first, as it does on Done. Under the releases, the folded Runs lists every deploy run of the project, newest first, with Environment (Any environment) and Status (Any status) to narrow it. A project with no deploy run yet reads No runs. Runs needs a plan with Production QA. Pull request links are not shown here; the task page lists them.

Select a task to open it beside the list. On a phone it opens full screen.

The Release step​

On the stage strip, the Release step, between Dev and Production or between any two stages with a branch each, is one icon: a truck on a blue disc. It turns while a release runs and goes red when the last one failed. It carries no count: the stage before it shows what waits. Hover it for the release's state, such as Queued or 1/2 approvals. Select it, as you would a stage, to list what waits, with every release action in a row above the list. Select a stage to leave it. How to use them is in Release to production.

The Release step's bar: the Select all box, Dev → Production, 17/17 shipping, the cost, the tokens and oldest 28d, then Now, Release 17 and Connect deploys

ControlWhat it does
Why it waitsAbove the list, the same reasons as the step's chip, such as Frozen until Fri 18:00.
Task listThe changes waiting on the stage before it. With none ticked, everything ships; tick some to ship only those. An epic shows only the subtasks this release ships; one not yet finished reads Part in place of its persona. With the merge lane on, changes merged after its newest tested commit come last, with the testing mark, and can't be ticked. When only those wait, Release's hover reads Waiting for tests; with nothing at all, Nothing to release. Work a schedule, a trigger or an agent filed sits under a closed Automatic row at the end; folded, it still counts, Select all still ticks it and it still ships.
Select allThe box at the start of the bar. Ticks every change the list shows.
TitleAfter the box, when the bar knows both stages: the two stages, such as Dev → Production.
FiguresHow many changes ship of those listed, such as 17/17 shipping. +N after it counts changes your search or filters hide, or commits with no task, which ship too. Then the cost, the tokens, and the age of the oldest change. Hover each for its words.
WhenReads Now. Its clock picks a later time instead. During a freeze, it starts at the freeze's end; someone who may override the freeze can select the clock to switch it to Now, and the release then runs through the freeze.
TicketShown when the step needs a change ticket (Change ticket for ServiceNow). Jaah looks the key up and shows its status; Release N stays off for a ticket it doesn't know.
Release NReleases N changes, now or at the When time. Always on the bar: when it can't send anything it reads Release, greyed out, and its hover says why. It sends at once, with no confirmation. With the merge lane on and nothing ticked, someone who can edit the pipeline ships the changes not tested yet too, without the full tests; N counts them, and the hover says how many. Anyone else ships the newest tested commit only. When it ships untested changes or runs through a freeze, the Audit page records No reason given. See Release changes that have not been tested.
OverrideOn a queued or scheduled release held by a freeze, to someone who may release and edit the pipeline. Runs it through the freeze at once. The Audit page records the override with No reason given.
Release statusOnce a release is asked for, it takes the list over: the bar shows its state, such as scheduled, queued or running, and where it goes, with a moving line under it while it runs. Hover a queued release for what holds it. Under the bar, the release's own release row lists what it ships.
ApproveGives your approval. Shown only to people allowed to approve, never to the person who asked for the release.
RejectTurns the release down. Shown to the same people as Approve.
CancelWithdraws the release before it ships. It asks first, Cancel this release?: its changes go back to waiting. Cancel release confirms; Keep it lets it run.
RetryOn a release that failed before its merge, such as when its checks failed. Sends the same release again on the same pull request: its failed checks run again, then it merges. Hover text: Re-run the failed checks on the same PR, then merge it.
RunOpens the release's run page, with its jobs and logs. On a failed release, Release sends everything still waiting as a new release. See Release runs.
Open nodesShown while the release is queued and no node is online. Opens your nodes.
ChecksUnder the bar, the results of the checks run before the release and on the stage it leaves, such as Checks on Dev.
Connect deploysShown when the project's deploys are not tracked, so a release reads Released as soon as it merges. Opens Deploy tracking in the project's Settings › CI Pipeline (on a custom pipeline, under its Production stage). Once connected, a release finishes when its deploy run succeeds.

States​

StateMeaning
DraftNot started. Press Start to queue it.
QueuedStarted, waiting for a runner.
WaitingWaiting for a task it depends on to finish, or for a free runner slot. Hover its icon for the reason.
HeldAn epic that dispatches only the subtasks you press Run on.
StartingA runner is being dispatched.
RunningA runner is working on it.
AskingIt needs your answer before it can go on.
DeliveringYour answer is recorded and on its way to the runner.
FailedIt used up its attempts. It needs your attention.
PausedStopped by hand. Review it, then start or reset it.
DoneFinished.