Approvals

How a stage is signed off, who may do it, and what happens when you reject one.

Two ways a workflow asks for a decision#

A stage held for approval. Any stage can be set to park itself once its work is done. It names the teams who sign it off, separately from the teams who take part. Anybody can help design something while Product has the final say.

An approval stage. A stage that is nothing but a sign-off, for a decision that belongs to no single stage, such as agreeing that a whole change is ready.

Finding what is waiting for you#

Stages waiting for your team’s approval are in My work, whether or not you own the work item. If you have turned notifications on, you are told as well.

Approve#

Open the work item, read what the stage produced, and approve it. The work moves to the next stage straight away.

A Diagnose stage waiting for approval. Approve is at the top right, beside its documents.
A Diagnose stage waiting for approval. Approve is at the top right, beside its documents.

If you are both doing a stage and one of its approvers, the button is Approve and continue, so you do not have to send the work to yourself.

Reject#

Rejecting takes a reason, and the reason goes back with the work.

What you rejectedWhere the work goes
An agent stage that holds its own approvalBack to that stage’s agent.
A separate approval stageBack to the nearest agent stage before it.
A manual stage, such as a taskBack to the person who did it.

The agent reads your reason and revises its work. When it is done, the stage comes back to you.

Who may approve#

  • Members of the stage’s approving teams.
  • A project admin or an admin, for when the usual person is away.

Every decision is recorded with the name of who made it. If that person is not on the approving team, the page says so.

QA is two decisions#

A QA review stage separates finding problems from deciding what to do about them. The testing team passes or fails each acceptance criterion and logs what they found. A different team decides which of those bugs are fixed now. See Acceptance criteria and QA.

Approving a pull request#

The pull request itself is approved on your repository host, not in Eido Build. The merge stage shows what it is waiting for, such as “Waiting for approval” or “Changes requested”, and merges once the pull request is approved. See Branches, builds and pull requests.

Popular

Your first work itemRaise an enhancement and follow it through triage, the agent stages, approval and the merge.User guideHow a workflow runsThe stages a work item passes through, who has each one, and what each status means.User guideAcceptance criteria and QAWriting down what done means, testing a change against it with evidence, and deciding what happens to the bugs that turn up.User guideCutting a releaseFreezing a release, running its checks, deciding what to do about what they find, and shipping it.User guideOdieThe assistant on every page. It reads everything you can read, and anything it wants to change becomes a card for you to press.User guideCosts and budgetsWhat agents cost, where to see it, and the caps that stop a stage, an agent or a month from overspending.AdministrationIntegrations for agentsLetting agents act in other systems by granting them specific actions, without ever handing them a credential.AdministrationLicensingHow Eido Build checks its licence, what it sends when it does, and what to do if it locks.Install and licence