Shape the backlog
Capture upcoming work, order it, and attach types, estimates, and owners before committing anything to a Sprint.
Backlog, time-boxed Sprints, Projects, and board Views live in the same Space. The team commits the scope, Agents execute what was planned, and progress stays visible to everyone.
How it works
Agent execution lands inside the project management the team already runs. Work that is not on the board is not in the cycle.
Capture upcoming work, order it, and attach types, estimates, and owners before committing anything to a Sprint.
A Sprint is a Space time box. Pull work in, watch capacity, and keep people and Agents on the same committed set.
A Project groups related Tasks across Sprints for one goal or release.
Project Workflow
Every project management surface writes to Tasks. Agents do not keep a separate one.
The board holds the committed Tasks in a Space. Teammates, Crews, and Agents share one Assignee control, so who is executing is visible at a glance.
A Sprint groups the committed Tasks in a Space. Once it starts, work in progress and scope changes stay visible instead of being buried in chat.

A Project is an optional grouping for related Tasks. Use one when a goal, launch, or workstream should stay visible across Sprints.

Saved Views keep board, list, grouping, and filters ready, so the team does not rebuild the same query every week.

The project management system
Backlog, Sprint, Project, and View are how a Space runs project management. Agents execute inside that scope.
Uncommitted work, ordered and typed, waiting for the next cycle.
A Space time box of committed Tasks for people and Agents.
Optional grouping for an initiative, release, or workstream.
The path Tasks take through the statuses a Sprint or View tracks.
Saved boards and filters, ready to open without rebuilding them.
Assigned Agents execute committed Tasks; they do not set up a system of their own.
Connected features
Triage feeds the backlog, Agents run committed Tasks, and Automations handle what repeats.
Quality of life, built in
If Agent work cannot appear on the Sprint board, it is not part of project management.
Shape the backlog, commit a Sprint, and let assigned Agents execute on the same board.
Start
Fill the backlog, start a Sprint, and assign Agents to committed work so execution stays inside project management.
Create Tasks with types, estimates, and owners. Keep uncommitted work out of the current Sprint.
Pull in what the team can finish this cycle. People and Agents share that committed set.
Put Agents on the Tasks that should run. Review still happens on the same board.
FAQ
No. A Sprint is a Space time box of committed work. A Project is an optional grouping for an initiative that can span several Sprints.
No. Agents execute Tasks that already live in the Space. If the work is not on the backlog or Sprint, it is not in project management.
A Sprint is the time box. A View is a saved way to look at Tasks — a Sprint board, a backlog list, or a Project grouping.
You can keep Jira connected and still run Agent execution in HiFox. Synced issues become Tasks that can sit in a Sprint and be assigned.
It remains a Task: move it to the next Sprint or return it to the backlog, and the history stays on the item.
Only when they create or update Tasks the Sprint tracks. Recurring runs that are not Tasks keep their history on the Automation.