Ubirimi ubirimi
AGL Scrum & Kanban

A board that does not move the issue is theatre.

Agile is the plan and work surface for Yongo issues. Each board is scoped by a saved filter. Columns map to statuses you already configured. Drag a card and you fire a real transition — the navigator cannot disagree with the wall, because they are looking at one record.

Included in every account. Agile is not on the default product top bar until an administrator enables it for the tenant — the code is in the suite; if you do not see Boards after sign-in, ask us to turn it on.

Start a 15-day trial Why Agile
Backed by
Yongo issues
Scope
A saved filter
Drag
A real transition
Views
Plan · Work · Report

Why Agile

Plan visually without creating a second source of truth.

A useful board should make delivery easier to understand, not create a decorative copy of the tracker. Agile turns the Yongo issues teams already trust into planning, work, and reporting views, so a move on the board is a real change everywhere.

  1. 01
    See the work in context

    Scope a board with a saved filter, map columns to your statuses, and use swimlanes to make the team’s priorities legible.

  2. 02
    Plan with less ceremony

    Keep backlog, future sprints, and the active sprint on one surface, with the same issue keys people use everywhere else.

  3. 03
    Trust what the board says

    Dragging a card executes the configured workflow transition, including its conditions, instead of painting over the real state.

AGL-BOARD

A board is a filter, plus columns, plus swimlanes.

Create a board, point it at a Yongo filter, map columns to statuses, set swimlanes. Mix projects or keep a single team. Delete it when the team dissolves — the issues remain.

  • Filter-scoped agile_board.filter_id points at a saved Yongo filter. The wall can only show what that filter already trusts.
  • Columns CRUD and position. Each column is a set of statuses. The last column is “done” for the backlog, by position, not by an English name.
  • Swimlanes Slice the work view without inventing a second tracker.
  • Configure List, add, edit, delete. The board is an artefact you own, not a template you rent.

AGL-PLAN

Plan is backlog, future sprints, and the one that is started.

One surface: the started sprint, sprints that have not started, and the backlog. An issue appears in the backlog when it matches the filter, is top-level, is in no sprint, and is not in the last column.

  • Top-level only Sub-tasks never appear as backlog rows. They live on the parent issue, where Yongo already shows them.
  • Sprint membership is global Planned on another board’s sprint, it will not show in this backlog. That is honesty, not a bug — one issue, one sprint seat.
  • Move in and out Add to a sprint, send back to the backlog, start, complete, delete a sprint. The issue does not change database.

AGL-WORK

Work is the live wall. Dragging is a transition.

The work view reflects issue state as people drag cards across columns. Transition lookups come from Yongo. If a workflow condition refuses the move, the card does not pretend it moved.

  • Drag and drop Out-transitions are fetched from the same workflow the issue view uses. The wall is not a parallel state machine.
  • Parent / sub-task checks Completion respects the parent issue. You cannot “done” a card the workflow would refuse on the issue itself.
  • Same assignee, same key PLATFORM-184 on the wall is PLATFORM-184 in the navigator. Copy the key. Open the issue. Come back to the board.

AGL-RPT

Reports look at the same issues the sprint does.

Sprint-oriented reporting on the tracker you already trust. No export into a methodology tool that forgets your statuses.

  • Sprint reports What entered, what left, what is still in the last column — in your names, not ours.
  • Scrum or Kanban Use sprints, or a board that is just this team’s cut of the tracker. The point is the shared record, not the poster on the wall.

Same house

The board is another door into the issue.

YNG

Yongo

Types, screens, workflows, search. The object the board is looking at.

HLP

Help Desk

Queues are another cut of the same issues, with SLA clocks on top.

DOC

Documentador

The sprint goal belongs on a page. The work stays on the board.

UBI

The suite

Included. No Agile SKU hiding behind a higher plan.

Index

Everything on this board

  • AGL-1
    Scrum & Kanban boards Create boards, map columns to statuses, and configure swimlanes.
  • AGL-2
    Plan view Backlog, future sprints, and the active sprint in one planning surface.
  • AGL-3
    Work view A board that reflects live issue state as people drag work across columns.
  • AGL-4
    Sprints Start, complete, and move issues between backlog and sprint.
  • AGL-5
    Reports Sprint-oriented reporting on the same issue data your tracker already trusts.
  • AGL-6
    Filter-scoped boards Each board is powered by a Yongo filter, so you can mix projects or keep a single team focused.
  • AGL-7
    Real transitions Dragging a card runs a Yongo workflow transition, including conditions.
  • AGL-8
    Top-level backlog Sub-tasks stay on the parent. The plan view does not flatten the job into noise.

The deal

Agile is not an add-on SKU.

The board ships with the suite. Fifteen days, every room, no card on the form.

Create an account See pricing

  • +Columns map to your statuses — not a fixed To Do / Done
  • +Sprint membership lives on the same issues as the navigator
  • +Sub-tasks stay on the parent; the backlog shows top-level work
  • +Updates stay free