A customer cannot finish onboarding. An important decision keeps returning to the leadership meeting. A handoff breaks down between teams. These problems need more than a message that someone might remember later.
Wave Issues gives teams a shared place to capture problems, assign responsibility, and follow them through to resolution. Organize issues into groups, distinguish short-term problems from long-term improvements, set priorities and due dates, and keep the supporting discussion beside the work. List and board views help the team decide what needs attention next.
Watch the Wave Issues showcase
The 48-second showcase uses actual Wave UI components with fictional sample data from Northstar Studio: six issue groups, six teammates, three teams, and 20 launch issues. The featured group contains 12 short-term issues and eight long-term improvements. Six issues are completed and 14 remain open. Names, dates, findings, and results are illustrative.
What is Wave Issues?
Wave Issues is the issue-tracking tool inside Wave. It helps teams make a problem visible, understand its context, name the person responsible for moving it forward, and keep a record of the next steps. An issue can describe a product defect, a customer experience problem, an operational bottleneck, or a decision that needs attention.
An issue group holds related problems and has its own owner, teams, status, priority, and planning dates. Each issue has its own assignee, type, priority, due date, estimate, labels, and completion status. This separates responsibility for reviewing the group from responsibility for resolving an individual problem.
In the demo, Jordan oversees Customer Launch. Sam handles an account-access problem, Riley clarifies onboarding ownership, and Maya resolves a mobile layout issue. The shared group keeps those problems visible without assigning every resolution to its owner.
Organize problems into issue groups
1. A central issue group catalogue
The Issues catalogue shows each group's title, health, priority, owner, target date, and status. Scan the overview to identify which area needs attention before opening its detailed work.
The sample workspace includes Customer Launch, Product Quality, Customer Experience, Operations, Leadership Decisions, and Growth Experiments. A useful group name describes the area the team reviews together.
2. Issue group creation and naming
Create an issue group with a title and associated teams. The creation form also provides an emoji and properties for status, priority, owner, start date, and target date. Give the group a specific purpose so teammates know where a newly discovered problem belongs.
3. Team associations
Associate a group with the teams involved in resolving its issues. Customer Launch can involve product and customer success, while Leadership Decisions can support a different review. Teams provide organizational context alongside individual ownership.
4. Group ownership
Assign an owner to keep the group organized and its review moving. The owner can check that new issues have enough context, a responsible teammate, and a next step. Individual issue assignees remain separate from this overall responsibility.
5. Group status and priority
Issue groups support Backlog, Planned, In Progress, Completed, and Cancelled statuses. Priority is a separate field with No Priority, Urgent, High, Medium, and Low options. Use status for the group's stage and priority for its relative importance.
6. Start dates and target dates
Set the group's start and target dates to give the review a timeframe. Target dates appear in the catalogue. Individual issues also have due dates, so a launch group can have a month-end target while a critical fix is due earlier.
7. Favorites and recognizable groups
Favorite the groups you review frequently to make them easier to return to. Favorite cards appear above the catalogue, with favorites also available in workspace navigation. Group naming and emoji controls help distinguish workstreams at a glance.
8. Catalogue search and filters
Search issue groups by name, or filter the catalogue by status, owner, priority, and target date. Display controls manage the catalogue presentation, including favorites. A focused overview helps when several teams maintain their own groups.

Make every issue actionable
9. Clear issue titles and descriptions
Give an issue a title that names the problem and a description that explains its impact. The featured example is “Resolve invitation emails arriving late.” Its description explains that delayed invitations block the first login and create extra support follow-up, then defines the expected resolution.
10. Short-term and long-term issue types
Classify issues as Short-Term or Long-Term. Short-term issues can capture immediate obstacles; long-term issues can hold problems requiring broader investigation or a later decision. Type is independent of priority, so a long-term problem can still be important.
The demo separates invitation delivery and account access from longer-term improvements such as simplifying ownership across customer teams. That makes it easier to keep today's blockers and future improvements visible in the same group.
11. Individual assignees
Assign each issue to the teammate responsible for moving it forward. The assignee appears in the row, board card, and detail panel. A named owner makes the next follow-up clear, even when several people contribute to the solution.
12. Open and completed issues
Individual issues use Open and Completed states. Mark an issue complete when the agreed resolution has been checked, and reopen it when more work is needed. These states are distinct from the broader planning statuses available on an issue group.
13. Issue priorities
Set priority independently for each issue. The sample account-access problem is Urgent, while invitation delivery is High. Priority helps the team decide what to discuss first without changing the issue's type or the group's overall status.
14. Due dates
Add a due date when there is a meaningful commitment. Dates are visible beside the issue and in its properties. Use them to plan a resolution checkpoint or prepare a review of outstanding work.
15. Estimates
Select an estimate from the workspace's configured options. The sample uses Small, Medium, and Large to support an effort discussion. Available values depend on the organization's configuration; an estimate is separate from urgency and completion.
16. Labels
Apply labels to identify themes across the group. Launch, Customer Success, Engineering, and Research help organize the fictional examples. Labels provide another way to find related issues without changing their owner or type.
17. Inline property editing
Use controls beside an issue to adjust properties such as assignee, type, priority, estimate, labels, and due date. Board cards also expose key editable properties. Quick changes can happen during a review, while the detail panel provides room for the reasoning behind them.
18. Moving an issue between groups
The Issue Group property lets you change where an issue belongs. A problem first captured in Customer Launch might belong in Product Quality for continued follow-through. Keep its description and notes clear so the receiving group understands the context.
Choose the right view for the conversation
19. List view
List view presents issues in compact rows with their properties alongside them. It is useful for scanning a larger group, checking dates, and comparing ownership. The showcase groups the 20 sample issues into Short-Term and Long-Term sections.

20. Kanban board view
Switch to Board through Display to review the same issues as cards in columns. Cards give the title and supporting properties more space. The sample priority board makes the urgent account-access problem easy to find.
21. Grouping by issue type, status, priority, or assignee
Choose Issue Type, Status, Priority, or Assignee as the grouping field. Each answers a different review question: what needs attention now or later, what is complete, what is most urgent, or who is responsible. Changing the view gives another perspective on the same issues.
22. Group visibility and counts
Display controls let you show or hide groups, and group headings show issue counts. List groups can also be collapsed. A team can focus a short review on the relevant group while keeping the rest available for later.
23. Ordering and moving work
List and board interactions support arranging issues and moving them across supported groups. The meaning of a move follows the grouping: a status column represents status, while an assignee column represents ownership. Use these interactions deliberately when reviewing priorities and responsibilities.
24. Search and detailed filters
Search by issue name or ID. Issue filters include Status, Assignee, Creator, Issue Type, Estimate, Priority, Label, Due Date, Created Date, and Updated Date. These controls help answer specific questions, such as which high-priority short-term issues are assigned to a teammate or which problems were recently updated.

Keep the context and resolution together
25. Issue detail panels
Open an issue to review its title, description, attachments, and properties in one panel. Sub Issues, Comments, Notes, and Activity tabs keep the supporting work nearby. Previous and next controls help you move through issues during a review.
26. Sub-issues
Split a problem into smaller resolution steps with sub-issues. Each can have a name, completion state, assignee, priority, estimate, due date, and notes. The parent issue shows a completed-sub-issue count, such as 2/4.
The invitation example includes reviewing delivery logs, reproducing the delay, adding retry controls, and validating delivery with pilot accounts. Two steps are complete. The remaining steps have owners and dates, making the path to resolution concrete.
27. Notes
Use the rich Notes editor for findings, working hypotheses, decisions, and the next checkpoint. In the demo, the notes distinguish an observed delivery delay from a hypothesis about retries. That distinction helps the next teammate understand what is known and what still needs investigation.
28. Issue and group comments
Discuss a specific problem in its Comments tab. The issue group also provides a comments entry point for conversations about the group as a whole. Use the appropriate level so a later reader can find both the issue-specific answer and the broader decision.
29. Attachments and supporting resources
Add media and files to support the issue. A screenshot, example, or brief can make a problem easier to understand than a title alone. Keep relevant evidence with the description and discussion so teammates can return to it during resolution.
30. Activity history
Activity tabs provide a place to review recorded changes on issues and issue groups. Use the history to understand how the work evolved. Notes and comments can explain the reasoning behind a change when a recorded event alone is not enough.
Review progress and keep the group useful
31. Scope and completion totals
Issue group details shows Scope, Incomplete, and Completed totals with percentages. The sample group contains 20 issues: 14 incomplete, or 70%, and six completed, or 30%. These figures describe issue completion, rather than effort, severity, or business impact.
32. Assignee, label, status, priority, and type breakdowns
Explore counts through Assignees, Labels, Status, Priority, and Issue Type tabs. These breakdowns help focus the review on the corresponding issues. The sample Issue Type breakdown shows 12 short-term issues and eight long-term issues.
Counts provide useful prompts for discussion. They do not imply equal effort: one unresolved issue can require more work than several smaller issues combined.
33. Health updates
Post a group update to explain progress, risks, and the next checkpoint. Health is visible in the catalogue, while the update timeline keeps the written assessment with its author and date. A group can be On Track while many issues remain open if the team is meeting its plan.
The fictional timeline shows an At Risk update when invitation delays surfaced, followed by an On Track update after the team established owners and resolution steps. Health is a team assessment, separate from the completion percentage.
34. Links and IDs
Copy an issue or issue group URL to direct teammates to the relevant record. Copy ID provides a compact reference for meeting notes or follow-up. Sharing a reference does not change the workspace permissions required to access it.
35. Notification preferences
The issue group's details menu includes Notifications. Use the available preferences to choose how you follow issue activity. Notification delivery depends on the channels and preferences configured in Wave.
36. Archive, delete, and selection controls
Archive issues or groups that no longer belong in active work. Delete controls are also available, and selection checkboxes support managing multiple records through the available selection actions. Choose the action that fits the intended cleanup and review the confirmation before removing work.
37. Issues across the workspace
Issues can be reviewed in personal, team, manager, and meeting contexts as well as their issue group. This lets teams bring the relevant problems into their operating rhythm. Available actions depend on the view and its editing permissions.

A practical issue-resolution workflow
Start with one issue group your team can review regularly. The Customer Launch example follows a simple sequence:
- Capture the problem. Write a specific title, explain the impact, and describe what a useful resolution would look like.
- Classify and prioritize. Choose Short-Term or Long-Term, assign an owner, and set a priority. Add a due date when there is a real commitment.
- Investigate and split the work. Keep findings in Notes and use sub-issues for steps that need their own owners or dates.
- Review the next action. Use the priority board for triage, an assignee grouping for ownership, or issue-type groups to separate immediate and longer-term concerns.
- Verify and close. Check the agreed resolution before marking the issue complete, then update the group's health and next priorities.
For the invitation problem, completion means more than finishing a code change. The team also validates the customer experience. The issue record gives that final check a visible place in the workflow.
When to use Issues, Projects, Lists, or Goals
Use Wave Issues when the starting point is a problem, blocker, or unresolved question that needs ownership and follow-through. Use Wave Projects to organize a defined delivery effort and Wave Lists for a flexible queue of requests, ideas, or checklist items.
Wave Goals holds the outcomes the team wants to achieve. Wave Meetings provides a place to review the relevant work together. Keep the purpose of each group clear so problems reach the people who can resolve them.
Wave Issues frequently asked questions
What is Wave Issues used for?
Wave Issues helps teams track problems, blockers, operational concerns, and unresolved decisions. It combines issue groups, ownership, priorities, dates, views, supporting context, and progress reviews.
Can Wave Issues track more than software bugs?
Yes. An issue can describe a customer experience problem, a handoff gap, or a business decision as well as a product defect. Use the description, type, labels, and group to make its purpose clear.
What is the difference between short-term and long-term issues?
They are issue types used to distinguish immediate problems from longer-term concerns. Type is separate from priority, status, and due date. You can group and filter issues by type.
Does Wave Issues have a Kanban board?
Yes. Display provides List and Board views, with grouping by Issue Type, Status, Priority, or Assignee.
Can issues have smaller resolution steps?
Yes. Sub-issues support their own completion states, assignees, priorities, estimates, dates, and notes. The parent issue shows the completed count.
How does Wave Issues show progress?
Issue group details shows scope, incomplete and completed totals, percentages, and breakdowns. Health updates add a written assessment of progress and risk.
Can I keep discussions and files with an issue?
Yes. Issue details includes Comments, Notes, Activity, and attachment controls. The issue group also has its own comments and updates.
Is the showcase using real customer data?
No. It uses actual Wave UI components with fictional issues, people, dates, and updates in an isolated sample workspace.
Bring your team's next issue into Wave
Wave Issues gives a problem a shared home, a responsible owner, and a visible path toward resolution. Start with the issues already recurring in your team conversations, add enough context to act, and make their review part of your regular rhythm.
Get started with Wave or explore the workspace at ourwave.io.



