Skip to main content

Tickets

Web vs mobile: Tickets live under More → Tickets (not a root tab) because mobile prioritizes alert and device triage. Create, update, comment, and assign on mobile; bulk admin and NinjaOne deep config remain on PanelOne web.

Navigation: More → Tickets

PanelOne Mobile provides full ticket browse, create, update, and comment workflows with offline queue support for field engineers.


Overview

The Tickets screen provides:

FeatureDescription
StatsOpen, in-progress, resolved counts
FiltersStatus, priority, assignee, source, open-only
SearchTitle, number, client
CreateToolbar + button (online)
DetailFull ticket view with comments and metadata

Reaching Tickets

Tickets are intentionally under More, not the root tab bar:

  1. Tap More in the tab bar.
  2. Under Operations, tap Tickets.

Alternative paths:

PathWhen
Global searchSearch ticket number or title
Push notificationTap ticket alert
Deep linkpanelone://tickets/{id}
Client detail → Tickets tabClient-scoped list
Dashboard drill-downOpen tickets stat card

Ticket List

Each ticket row shows:

  • Priority badge — Urgent (red), high (orange), medium (yellow), low (gray)
  • Ticket number — Auto-generated reference
  • Title — Subject line
  • Client name — When no client scope active
  • Assignee — Resolved team member name
  • Status — Open, in progress, resolved, closed
  • Source — Manual or integration (NinjaOne icon)
  • Timestamp — Created date

Tap a row to open ticket detail.


Filtering

FilterOptions
StatusOpen, in progress, resolved, closed, all
PriorityUrgent, high, medium, low, all
AssigneeTeam members or unassigned
SourceManual, NinjaOne, all
Open onlyQuick toggle for active tickets

Filters persist per organization.


Creating a Ticket

  1. Open More → Tickets.
  2. Tap + in the toolbar.
  3. Fill in the create sheet:
    • Title (required)
    • Description
    • Client (defaults to active client scope if set)
    • Priority — Low, medium, high, urgent
    • Assignee — Optional team member
  4. Tap Create.

Online vs Offline Create

ConnectivityBehavior
OnlineTicket created immediately via API
OfflineQueued as ticket_create; appears locally until sync

Queued ticket creates flush when connectivity returns. See Offline & Sync.


Ticket Detail

Ticket detail shows:

SectionContent
HeaderTicket number and title
Status pickerChange status with optimistic update
Priority pickerChange priority (queues offline if needed)
Assignee pickerAssign or reassign
Client linkNavigate to client detail
Portal metadataClientOne portal fields when present
AttachmentsView ticket attachments
CommentsThread with author names
TimestampsCreated, first response, resolution

Updating Fields Offline

Priority, assignee, and status changes queue as ticket_field_update or ticket_status_update writes when offline. The UI updates optimistically and syncs on reconnect.


Comments

Add comments from ticket detail:

  1. Scroll to the Comments section.
  2. Tap Add comment or the comment composer.
  3. Enter your note and submit.

Comments queue as ticket_comment when offline.

Comment authors display resolved team member names from the org directory.


Attachments

View attachments synced from PSA or manual uploads. Uploading new attachments may require connectivity — check ticket detail when online for full attachment workflows.


Client-Scoped Tickets

When client scope is active or viewing client detail → Tickets tab:

  • List filters to that client's tickets.
  • New tickets default to the scoped client.

Push notifications and deep links can open a specific ticket by ID. If the ticket isn't in the local list cache, the app fetches by ID before showing detail.

Supported routes:

  • panelone://tickets/{id}
  • panelone://more/tickets (list)
  • Universal link: https://app.panelone.dev/tickets/{id}

See Push Notifications & Deep Links.


Tips & Best Practices

  • Bookmark More → Tickets — It's the primary path despite not being a root tab.
  • Use global search for ticket numbers during phone calls.
  • Update priority and assignee in the field — Changes queue offline safely.
  • Add comments before leaving site — Documents work done for the team.