Skip to main content
Opening a ticket brings you to the Ticket Detail view, which presents everything NOCK collected at the moment your user submitted their feedback. The detail view is divided into clearly labelled sections so your team can quickly understand the problem, reproduce it, and coordinate a response — all without leaving NOCK.

Submitted content

At the top of the page you’ll find the information the user typed directly into the widget:
  • Title — A short summary of the feedback as written by the user.
  • Description — The full text of the user’s message.
  • Category — The feedback type the user selected (Bug, Feature, General, or a custom category you’ve configured).
This is the raw voice of your user, unmodified.

Status

The current status of the ticket is displayed prominently near the top of the detail view. Your team can change it at any time as work progresses.
1

Click the status badge

Find the status indicator near the ticket title and click it to open the status dropdown.
2

Choose a new status

Select Open, In Progress, Resolved, or Closed depending on where the ticket stands.
3

Confirm the change

The badge updates instantly. No additional save step is required.
Status changes are reflected immediately in the Tickets list view and for all team members viewing the same ticket.

Auto-captured context

NOCK automatically records a snapshot of the user’s environment when they submit feedback. You don’t need to ask the user for this information — it’s captured silently in the background.
FieldWhat it tells you
Page URLThe exact URL the user was on when they submitted the ticket.
BrowserThe browser name and version (e.g., Chrome 124, Safari 17).
Operating systemThe user’s OS and version (e.g., macOS 14, Windows 11).
ViewportThe width × height of the user’s browser window at submission time.
The page URL is especially useful for reproducing bugs — you can navigate directly to the same page the user was on when the issue occurred.

Screenshots

If the user attached one or more screenshots when submitting the ticket, they appear in the Screenshots section. Click any thumbnail to view the full-size image. Screenshots are stored securely and are only accessible to members of your team.
Screenshot capture in the widget is optional and can be enabled or disabled in Project Settings.

Console logs

When console log capture is enabled for your project, NOCK records browser console output at the time of submission and attaches it to the ticket. This section displays each log entry with its level (log, warn, error) and message text. Console logs are particularly helpful for diagnosing JavaScript errors that a user might not know how to describe — the stack trace tells the story for them.
Console log capture must be turned on in Project Settings before it appears in new tickets. Tickets submitted before the feature was enabled will not have log data.

AI follow-up Q&A

If AI enhancement is enabled for your project, NOCK may automatically generate follow-up questions based on the user’s submission and present them to the user before they confirm their report. The user’s answers are attached to the ticket in this section as a structured Q&A transcript. This can surface important details — reproduction steps, expected versus actual behaviour, frequency of occurrence — that users might otherwise forget to include.
Enable AI enhancement in Project Settings to start collecting richer, more actionable bug reports automatically.

Linked Linear issue

If you have connected the Linear integration for this project, a Linked Issue section appears on the ticket detail page. When a Linear issue has been created from this ticket, the section shows the issue identifier, title, and a direct link to open it in Linear. If no issue has been linked yet, you can create one directly from this view with a single click.
The Linked Issue section only appears when the Linear integration is active for your project. See Connect Linear to set it up.

Internal comments

The Comments section at the bottom of the ticket detail page is a private space for your team. Use it to coordinate work, share findings, flag blockers, or leave context for teammates who pick up the ticket later. Comments are never visible to the user who submitted the ticket.
1

Scroll to the Comments section

Find the internal comments area at the bottom of the ticket detail page.
2

Type your comment

Click the comment input field and type your message.
3

Post the comment

Press Enter or click Post to save your comment. It appears in the thread immediately, visible to all team members.

Tickets List

Go back to the full tickets list to filter, search, and triage feedback.

Project Settings

Enable screenshots, console logs, AI enhancement, and more.