BroodBox features and progress

Use the IT-Labs account you already have; Brood has no separate password to remember.

Closing a task or confirming a merge asks you to prove it is you once more, then leaves you alone for about 15 minutes.

A banner tells you, and everyday work on the board goes on for a time your company sets. Steps that need IT-Labs wait until it is back.

View-only people read everything but see no buttons they cannot use.

One company never sees another's tasks, code or reports; our own tests check this on every change.

A Help link at the top of each page opens a short manual in plain words for exactly that page.

Every open task that is in no sprint, with the first one on top; move a task up or to the top in one click.

Plan a sprint, start it, and close it, choosing where unfinished work goes. Finished work stays to show what it delivered.

See a sprint's tasks in columns, its goal and dates, and how many tasks and points are done.

Name the steps your team really uses, choose which moves are allowed, and the board shows one column for each.

Add text, number, date, pick-list or person fields, such as a customer or a cost, to all tasks of a project.

Tick up to 200 tasks and move, assign, plan or drop them together. If one cannot change, none do, and you see why.

Make a repo in a project and clone and push over a secure web address with your API key. Your code stays with Brood.

Give each helper its own key that ends on a date you set; end one at once without touching the others. On the dev box this works inside the server only.

Work for a task goes on a branch named after it, so code, task and tests always belong together.

Brood runs your tests on exactly the code that was pushed, within time and memory limits, and shows passed or failed on the task.

A red run gets a plain summary of what failed on the task. Without AI you still get the list of failures. Off until your company switches the local model on.

Brood suggests an assignee from your people and helpers; you decide. Works from simple rules, and a local model can help when it is on.

The Merge button appears only when the tests are green and the task is in review. Pressing it is your yes, and the task closes as done.

Pushes straight to main are refused with a plain message. If the branch changed after you looked, the merge is refused so you only agree to what you saw.

Make a version, put tasks into it, and release it. Open tasks can move to the next version in the same step.

Each version page lists its finished tasks by type, and one click gives a file to paste into your own release page.

See whether work piles up faster than it is finished, and how long finished tasks took from start to approval.

See what each sprint took on and finished, and day by day how much is left. Charts come with a table that screen readers read out.

Bring titles, texts, types, priorities, labels, comments, links and open sprints from an exported file. Brood never contacts the other tracker.

Statuses, types, priorities and people are matched for you to review. Nothing is created until you confirm, and an import can be cancelled.

Run the same file again and the tasks made before are updated, not doubled. Imports wake nobody and send no notifications.

Bring a repo's main branch, tags and issues into a Brood repo in one fetch, with the issues as tasks. The outside host is used for import only.