Issues Hub

The Issues Hub gives you a cross-board view of all tickets you have access to. Instead of checking each board individually, you can see everything in one place -- filter, sort, and organize tickets across your entire workspace.

Accessing the Issues Hub

Click Issues in the sidebar (in the My Area section) to open the hub. It shows all tickets from all boards you have access to.

Views

The Issues Hub offers three different views to help you work the way you prefer:

List view

The default view shows tickets in a flat, filterable list. Each row shows the ticket ID, title, status, priority, assignee, and board. Click any ticket to open its detail view.

Use the column configurator to show additional columns -- including Due Date, which displays each ticket's due date. The Due Date column is hidden by default; once enabled, click the column header to sort ascending or descending by due date and see what's due next across all your boards.

Board view

Switch to the board view to see tickets organized in Kanban columns by status -- just like a regular board, but spanning all your boards. This is useful for seeing the big picture across projects.

Pulse view

The pulse view is your personal work context -- it shows what is currently relevant to you. You'll see summary stats (active, blocked, and waiting counts), priority items grouped by attention reason (blocked, blocking others, due soon, waiting on external, stale), and recent changes to your tickets. It answers "What needs my attention?" and "What changed while I was away?"

Filtering

The Issues Hub supports powerful filtering to help you find exactly what you need:

• Boards -- show tickets from specific boards only
• Statuses -- filter by individual statuses
• Assignees -- show tickets assigned to specific people, yourself, or unassigned tickets
• Types -- filter by ticket type (Bug, Feature, Epic, or custom types)
• Epics -- show only stories belonging to one or several Epics. Pick multiple Epics to see their stories side by side -- useful for tracking the progress of a larger initiative that spans several boards. See Epics and Stories for how to attach tickets to an Epic.
• Milestones -- filter tickets by one or more milestones. Select multiple milestones to see their tickets side by side (OR logic). The section only appears on boards where the Milestones & Releases feature is enabled.
• Releases -- filter tickets by one or more releases. Works the same way as the milestone filter with OR logic and multi-select.

You can combine multiple filters and use quick filter presets for fast access. A "Show done" toggle lets you include or exclude completed tickets.

Bulk actions

You can act on many tickets at once from the list and board views instead of opening each one:

• Use the row checkbox to select tickets. Selection survives filter and pagination changes until you clear it.
• Once at least one ticket is selected, the bulk action toolbar appears at the bottom of the screen and lets you:
  • Change status for all selected tickets
  • Change assignee (or unassign) for all selected tickets
  • Change type -- assign the same ticket type to all selected tickets
  • Assign / remove epic -- attach selected tickets to an epic or remove the association
  • Add or remove labels -- deliberately not a replace: across a mixed selection, "give all of these urgent" does not mean "urgent is now the only label"
  • Set or clear priority
  • Set or clear the due date
  • Archive the selected tickets
  • Move to project -- including a selection that spans several projects
  • Delete the selected tickets after confirmation
  • Copy — copy selected issues to the clipboard as a numbered list (ticket ID, title, link). The result works directly as input for AI tools or as a task list.
• Up to 500 tickets can be changed per bulk action. Above 50 selected, Spedy asks for a confirmation before applying the change.
• A move always asks for confirmation, regardless of count: the tickets get new ticket keys and land in the target project's backlog. Ticket type and milestone survive only if they exist there too.
• A selection may contain tickets from several projects. Permissions are checked per ticket, and a failure only affects that ticket -- the rest of the selection goes through.
• Tickets on boards you do not have access to are silently skipped and reported back, so a broad selection never leaks access across boards.

Bulk changes behave like single edits

A bulk change takes the same path as individual edits. That means it fires notifications, activity entries, automations and live updates. Your colleagues' boards refresh immediately, and your automation rules apply to bulk actions too.

Creating several tickets at once

The Multiple tickets button next to the search creates a whole list in one pass.

1. Click Multiple tickets

2. Pick the project

3. Write one line per ticket into the Titles field:

   Rework the login form
   Fix the password reset mail
   Document the session timeout

4. Set the shared fields below -- type, status, assignee, priority, due date. They apply to every line; "Project default" uses the project's own setting.

5. Optional: click Check for a dry run. You see per line whether it would go through -- nothing is created.

6. Click Create ... tickets -- the button names the count

Notes:

• List markers at the start of a line (- , 1. ) are stripped and empty lines ignored, so a pasted list just works.
• Up to 100 tickets per pass, titles up to 200 characters.
• If one line fails, only that line is affected. The summary afterwards states how many were created and how many were not.