logo
WorkspaceManage Kanban Tickets

Manage Kanban Tickets

Track operational tickets through open, in-progress, resolved, and closed states.

Goal

Create, review, update, and move support tickets through their working states.

Before You Begin

Any user involved in operational issue tracking.

  • Roles: Admin, Manager, Operator
  • Entry points: /ticket-kanban

Begin on the Kanban page.

Preconditions

  • The user can view ticket data.

Steps

Open the kanban board

Open the kanban board.

Search or filter to find the right ticket set

Search or filter to find the right ticket set.

Create a new ticket when a new issue needs tracking

Create a new ticket when a new issue needs tracking.

Open a ticket card to review details

Open a ticket card to review details such as description, assignee, tags, and due date.

Move the ticket to the next status as the work

Move the ticket to the next status as the work progresses.

Revisit resolved or closed tickets when follow-up

Revisit resolved or closed tickets when follow-up is needed.

Decision Points

  • Whether a ticket should stay in the current column or move forward.
  • Whether a ticket needs a linked knowledge entry rather than only a discussion thread.

Expected Result

Tickets stay visible, prioritized, and organized by current working state.

Common Problems and Edge Cases

  • Search and ownership filters can hide tickets the user expects to see.
  • Closed or resolved tickets may still need reopening if the problem returns.

Use these page links to move laterally through the platform and keep context as you go.

Kanban

Track tickets, blockers, and work-in-progress items across the workspace.

Knowledge Base

Open reference material, operating notes, and shared team guidance.

Chat History

Review prior AI conversations and reopen context from earlier sessions.

Was this page helpful?

Last updated 2 weeks ago

Built with Documentation.AI