Work#
Project. A product and its repository. Almost every screen shows one project at a time, chosen in the project picker, or all the projects you can see at once.
Work item. One piece of work: a bug, an enhancement, a task. It has a key made of the project’s key and a number, such as PULSE-142.
Work item type. The kind of work. A type has a name, a colour and an icon, and it also decides how the work behaves: whether it gets a branch, whether it goes through triage, and whether it ships in a release. Your administrators can add their own types.
Customer. Somebody who asks you for things. Customers are shared across projects, and a work item can be for several of them.
Custom field. Something your organisation tracks on its work that Eido Build does not ship with, such as a department, story points or a planned date.
Process#
Triage. The list of everything that has been raised and not yet decided. Work is approved or rejected there once. See Triage.
Workflow. The stages a work item goes through, in order. Standard delivery is Design, Refine, Build, Code review, QA and Merge. A project can have several workflows.
Stage. One step of a workflow. A stage is one of:
- an agent stage, a conversation with an agent that produces documents or code
- a manual stage, where a person does something and then says it is done
- an approval, where a team signs off
- a QA review, where a change is tested against its acceptance criteria
- a system stage, which Eido Build performs itself, such as opening and merging a pull request
Acceptance criteria. The short list of things somebody will check before a work item counts as done. See Acceptance criteria and QA.
Release. A set of work that ships together. A release is planned until it is opened, then in progress while it is being built. A project can also be set to ship continuously, with no releases at all.
Queue and backlog. Work that has been agreed to and has not started is queued. The backlog is the part of the queue that is in no release yet.
People#
Team. A group of people, such as Product, Engineering or QA. A workflow stage names the teams that take part in it and, separately, the teams that approve it.
Owner. The person on each team who has a given work item. Owners are named when the work is approved at triage, and can be changed on the work item at any time.
Follower. Somebody who hears about a work item as it moves. You follow anything you raise, comment on, are assigned to or are mentioned in.
Agents#
Agent stage. An agent working on one work item, inside a workflow. Each stage starts a fresh session that is given the work item and the documents approved so far.
Standing agent. An agent that belongs to no work item and runs on a schedule instead. It writes a report and raises suggestions, which arrive in Triage. See Standing agents.
Workbench. Where an agent runs: a cloud sandbox with the project’s repository in it.
Odie. The assistant available on every page. See Odie.
Spend cap. The most a stage, an agent run or a conversation with Odie may cost. All caps are in US dollars.