Overview, runs, and action logs

Use Overview#

The Overview page summarizes projects, recently checked issues, proposed actions, deletions, pending approvals, and recent runs.

All authenticated organization roles can view organization data. Starting a run requires runs:trigger; confirming or executing a guarded run requires runs:execute. Administrators, Managers, and Scrum Masters receive those permissions by default.

To start an on-demand run:

1. Select Run Agent Now.
2. In Select Cycles to Run, choose the cycles to include.
3. Confirm the selection.
4. Keep the live terminal open until the run completes or reports an error.

The trigger can be disabled by server configuration. If the button is unavailable, an operator must check RUN_TRIGGER_ENABLED on the API.

Browse run history#

1. Open Runs.
2. Use the board, project, or status filters when available.
3. Select a run row to open Run #<id>.
4. Review status, timing, selected cycles, summaries, and observability panels.
5. Open the run’s Action Log for individual operations.

Run statuses are planned, blocked, executing, completed, and failed. Dry runs are labeled DRY-RUN.

Review an action log#

The action log can show the action type, target, before and after state, execution status, approval state, and API response.

If a run requires confirmation:

1. Read every proposed action.
2. Confirm the project and target identifiers.
3. Select Confirm & Allow Execution only when the run is intended for live execution.

Confirmation does not execute the run by itself. The current UI explains that the run must be invoked again through the trigger path after confirmation.

Export data#

Use CSV or PDF on Runs to export filtered run history. Use the same controls on an action log to export one run’s actions. Exports are organization-scoped and require an authenticated session.