Use issue views and backlog

You will learn how to choose between list, board, table, calendar, timeline, and backlog views when managing project work.

All of these surfaces show issues from the same project. Changing an issue in one surface updates it everywhere.

Start with Issues

Open a project and choose Issues.

Use Issues when you want to create, scan, filter, sort, and open work. The Issues area can show multiple surfaces, including list, board, table, calendar, and timeline.

If you are not sure where to start, use list view.

Use list view for scanning and triage

List view is best for reading titles, opening issues, and working through a queue.

Use list view to:

Review new work.
Open issue detail quickly.
Sort a project issue list.
Triage unassigned or unestimated issues.
Check whether titles and labels are clear.

Keep list filters narrow enough that the next action is obvious.

Use board view for flow

Board view groups issues by status. Drag a card to another column to change its status.

Use board view to:

Run daily standup.
See what is started, paused, done, or cancelled.
Move work through the project workflow.
Spot overloaded or stale columns.

If a status change requires a resolution or violates project transition rules, Tixio will guide or block the change.

Group the board into swimlanes

Use Group by beside the board sort control to choose:

None for the standard status-column board.
Assignee to compare each person's work, including an Unassigned lane.
Epic to compare initiative-sized work streams, including a No epic lane.

Your choice is saved for you on that project or project-scoped saved view. The URL also carries the choice when you share a board link.

Drag a card across assignee or epic lanes to update that field. A single drop can change both the lane and status. Epic-type issues cannot be placed inside another epic. Filters and the show-subtasks setting apply to every swimlane.

Read and configure WIP limits

When a status has a WIP limit, its board header shows current count / limit. The count follows the active filters. If the count exceeds the limit, the header is highlighted, but the limit is advisory and does not block a drop.

Project admins configure a status limit from the project's Statuses settings. Enter a positive whole number, or leave the field blank for no limit.

Use table view for field-heavy work

Table view is best when you need to compare and edit many fields.

Use table view to:

Show, hide, reorder, resize, and auto-fit columns.
Sort by fields such as key, title, status, type, priority, due date, estimate, creator, labels, custom fields, fix version, affects version, and resolution.
Edit fields inline.
Select multiple rows and use bulk actions.
Review large sets of issues without opening each one.

Table layout is remembered for you, so set up the columns that match your role. If your project uses custom fields, show those columns when comparing project-specific data such as severity, customer tier, review date, or support owner.

Use calendar view for due dates

Calendar view is best when dates are the main question.

Use calendar view to:

Review upcoming due dates.
Spot crowded days.
Reschedule issues by date when supported.
Prepare launch or follow-up calendars.

If an issue has no due date, it will not be useful in calendar view until you add one.

Use timeline view for sequencing

Timeline is the Gantt-style view for schedule shape, time spans, and dependency planning.

Use timeline view to:

Understand how work lines up over time.
Plan cross-team delivery.
Review dependencies and ordering.
Communicate rough schedules.

Timeline is most useful when issues have dates or related planning context.

Use Backlog for work not yet committed

Open the project and choose Backlog.

Use Backlog for:

Ideas that need triage.
Work that is real but not scheduled.
Requests that need owner, priority, labels, or estimate.
Issues that should wait for a future cycle.

Backlog should be reviewed regularly. If it grows without triage, important work gets buried.

Hide done and show subtasks

Some issue surfaces include display options such as hiding done issues or showing subtasks. Use them to reduce noise while keeping the underlying issue data unchanged.

Hide done when you are planning or triaging open work. Show done when you need completion context or want to verify what shipped.

Show subtasks when you need the full breakdown. Hide them when the parent issue is enough context.

Use sort and filters together

Sort answers "what order should I inspect this in?" Filters answer "what should be included?"

Good combinations:

Filter to unassigned issues, sort by created date.
Filter to active cycle issues, sort by priority.
Filter to bugs, sort by status.
Filter to a custom field value, sort by updated date.
Filter to issues with due dates, sort by due date.

Save repeated filter setups as views when you use them often. For search syntax and reusable views, read Find work with search and filters and Create and share saved views.

Use bulk edit carefully

Bulk edit is useful for repetitive changes, such as assigning a triage owner, adding a label, moving issues to a cycle, or changing status for a known set of issues.

Before applying a bulk action:

Confirm the filtered set contains only the intended issues.
Review selected rows.
Choose the smallest change that does the job.
Spot-check a few issues afterward.

Avoid bulk-changing status or priority when the selected issues have different meanings.

Pick the right surface

Use this routine:

Start in List when reading and triaging.
Switch to Board when discussing flow or status.
Switch to Table when editing many fields.
Switch to Calendar when due dates matter.
Switch to Timeline when sequencing matters.
Use Backlog when work is not ready for active planning.