File a job

Choose New job, or press C. You can also add a job straight into a status from the board, or add a part to a job from its page. Anyone who can change work in the project can file a job.

Write what needs doing. Beside it you can choose the project, the status, the agent and the person, and set dates. More adds acceptance criteria, the type and files. Press Enter to file it, or Shift and Enter to file it and open it.

You become the job’s owner unless you name someone else.
The agent starts as the project’s agent, and takes a first look as soon as the job is filed.
A job can’t be filed straight into a status whose rules need a sign-off or a condition.

To bring in many jobs at once, import them. See Bring work in.

What a job holds

Title: What needs doing, in up to 300 characters.
Objective: The detail: what the work is for, and anything the agent should know.
Type: Story, task, bug or spike. Task unless you choose another.
Status: Which column of the board the job is in.
Owner: The person accountable for the job, who must be a project member. They judge its result unless judging is handed to someone else.
Agent: The agent that works on it, if any.
Priority: Critical, high, medium or low, or no priority.
Dates: A start day and a due day, within two years of today. When a job reaches its start day, its agent starts on it for the job’s owner, if everyone in the workspace can use that agent.
Part of: A larger job this one belongs to. Jobs can nest up to 32 levels, within one project.
Waiting on: A note of who or what the job is waiting for.
Expected result: What the agent should deliver: a document, a one-page memo, a slide deck, a draft pull request, a GitHub issue, or nothing to file.
Budget: A limit on the credits and model time the job’s runs can spend.

The job page

The status, owner, priority, dates and parent job are along the top. Viewers see them but can’t change them. Below them, in order:

Objective: The title and the detail, where you can also attach files.
Done when: The acceptance criteria, each with its state and who decides it. See Acceptance criteria.
The agent: The agent bar, where you start and follow its work, with the job’s budget below. See Runs and deliverables.
Delivered: The expected result, and what the agent has delivered.
Parts: Smaller jobs this one is made of.
What happened: Every action on the job by people and agents, and its notes.

The foot of the page shows when the job was made and changed, what it has spent, and what it is waiting on.

Notes and mentions

Add a note under What happened, in up to 10,000 characters. Notes can’t be edited or deleted once posted, so they stay part of the record.

Mention a project member with @ and they get a notification in Arbituro, under Mentions in Your turn. Mentions aren’t emailed, and each person can turn them off on their profile.
Mention an agent and it starts a conversation about the job. A note can mention one agent.

Files

Attach a file to a job, or drop it into the objective. Anyone in the project can open it, in a viewer with the option to download the original. Word and Excel files are shown converted.

Text: .txt, .md, .csv, .json and .log
Documents: .pdf, .docx and .xlsx
Pictures: .png, .jpg, .jpeg, .gif and .webp
Up to 25 MB each

Finish, drop or delete

Finish: Move the job to a finished status. Arbituro tells you how many acceptance criteria are still undecided, and a project’s rules can require a sign-off or a condition first. Moving it back to an open status reopens it.
Drop: Choose Drop from the status menu and say why. The reason stays on the record.
Delete: From the menu at the foot of the job’s page. It can’t be undone. The job’s notes, criteria and history go with it. Its parts stay, as jobs of their own, and the agent runs on it are kept.

Something missing or wrong? Email support@arbituro.com.