jonta

Features

Everything a client-facing software team needs, in one product

Support and a client portal, boards and sprints, GitHub and deployments, release notes, incidents and uptime monitoring, a wiki and reporting. Every feature is included on every plan.

Support & client portal

Give clients a secure portal to raise and track requests, while your team works the same ticket through to release. Included on every Jonta plan.

Boards & workflow

Project-specific Kanban boards with client-facing column names, real-time updates, workflow rules, auto-assignment and work-in-progress limits.

Sprints & planning

Jira-style backlogs, multiple active sprints, epics, sub-tasks, estimates and versions, with burndown, velocity and time against estimate.

GitHub & deployments

Link GitHub commits and pull requests to tickets automatically, show CI status, and record every deployment with its environment, version and tickets.

Release notes

Generate release notes from the tickets in a version or deployment, email them to client contacts and publish them in the client portal.

Incidents & uptime

Run SEV1 to SEV4 incidents with a timeline and incident commander, monitor URLs automatically and keep clients updated by email, without a separate status tool.

Wiki & knowledge base

Knowledge spaces with nested pages, rich text, attachments, ticket links, version history and per-space permissions, included on every Jonta plan.

Reporting & DORA metrics

Track deployment frequency, lead time, change failure rate and time to restore per project, plus burndown, velocity, time in stage and a CSV audit log.

Security & permissions

Granular roles and permissions, project-based teams, optional two-factor authentication, failed-login protection, session visibility and a full audit log.

Jira & Confluence migration

Free migration from Jira and Confluence. Keep ticket numbers, comments, attachments, sprints, authors and timestamps, with dry runs and repeatable imports.

The full feature list

Support and ticket management

One ticket from request to resolution

No copying between a helpdesk and a development tracker.

  • The client support request and the development ticket are one record
  • Priorities, assignees, estimates, due dates and labels
  • Attachments, linked issues, watchers, epics and sub-tasks
  • Internal comments and a complete history

Dedicated client portal

Clients raise and track their own requests, and only see what you share.

  • Raise and track support requests
  • Rich descriptions, images and attachments
  • Clients choose a priority
  • List and board views
  • Talk directly with your team
  • See approved tickets, labels, releases and incident updates
  • Clients only see information made available to their company

Separate client and internal conversations

One stream for staff, with private notes that never reach the client.

  • Client correspondence kept apart from internal notes
  • Rich text with formatting, tables, information panels, images and video

Custom ticket types

Bugs, support requests and internal work are easy to tell apart.

  • Your own names, icons and colours for each ticket type

Boards and workflow

Flexible Kanban boards

Each project gets the workflow it needs, and boards update live.

  • Configurable columns with client-facing labels
  • Drag and drop, and move several tickets at once
  • Filter and group by assignee, sprint, ticket type, priority or release
  • Assignee swimlanes and assigning from the card
  • Real-time updates

Workflow rules and WIP controls

The process is enforced by the board, not by reminders.

  • Blocking or warning rules on columns or whole boards
  • Require an assignee
  • Automatically assign incoming work
  • Work-in-progress limits
  • Rules that apply only to selected ticket types

Sprint, backlog and epic planning

Jira-style planning without Jira.

  • Backlog, multiple active sprints, epics and sub-tasks
  • Estimates, versions and release notes
  • Move unfinished work to another sprint or back to the backlog when a sprint ends

Project-specific configuration

Every client engagement is set up its own way.

  • Ticket numbering, workflow and board configuration per project
  • Project team and client-facing columns
  • Time tracking switched on or off per project

Development and delivery

GitHub integration

Commits and pull requests appear on the ticket automatically.

  • Connect a project to its GitHub repository
  • Commits and pull requests that mention a ticket key are linked automatically
  • Tickets show related commits, pull requests, PR status, CI status and branches
  • Optionally move tickets when a pull request opens or merges, still enforcing workflow rules

Deployment tracking

Know what shipped, where and when.

  • Environment, version, git tag or commit
  • Status: started, succeeded, failed or rolled back
  • The tickets included and the CI run identity
  • Reported automatically by CI or recorded manually

Release notes

Release notes write themselves from the tickets you shipped.

  • Generated from the tickets in a version or deployment
  • Mark releases complete
  • Email summaries to selected contacts
  • Publish release information in the client portal

Delivery performance reporting (DORA-style)

See how healthy delivery is on every project.

  • Deployment frequency and lead time for changes
  • Change failure rate and time to restore service
  • Time spent in each workflow stage
  • An indicative performance band for each indicator
  • A delivery-health snapshot covering incidents, integration activity and connection health

Incident and service management

Incident management

Run incidents in the same place as the work that caused or fixes them.

  • Severity levels SEV1 to SEV4
  • Investigating, identified, monitoring and resolved states
  • An assigned incident commander and a chronological timeline
  • Links to the affected ticket or deployment
  • Internal and client-visible updates
  • Audited incident deletion
  • Publishing permission separate from incident-management access

Client incident notifications

Clients hear about incidents from you first.

  • Client users subscribe to client-visible incidents affecting their company
  • Email updates as the incident progresses

Automated uptime monitoring

Jonta notices when a site is down and opens the incident for you.

  • Scheduled URL checks with expected status code, interval, timeout and severity
  • Choose whether each check is visible to the client
  • Repeated failures can open an incident automatically
  • Consecutive successful checks can resolve it
  • 30 days of check history

Ageing and SLA alerts

Nothing sits forgotten in a column.

  • Flags tickets that have stayed in a stage too long
  • Flags incidents approaching or past response and resolution targets
  • No duplicate alerts, and alerts can be acknowledged

Operational health checks

Built to be run and monitored properly.

  • Liveness and readiness endpoints for hosting and monitoring systems
  • Graceful shutdown protects real-time connections during restarts

Client communication

Releases and client updates

Clients see what you delivered without you writing an email.

  • Organise tickets into versions and mark releases complete
  • Email release summaries
  • Publish released work in the client portal

Reliable email notifications

Important alerts are queued, retried and never silently lost.

  • New client tickets, assignments and status changes
  • Release summaries and incident updates
  • Account and security events
  • Staff control their routine notification preferences
  • Delivery retries, with failures visible to administrators

Teams and access

Project-based team management

The right people on the right projects.

  • Choose which internal users work on each project
  • Assignment limited to project members
  • Membership changes recorded in the audit trail

Granular roles and permissions

Decide exactly who can see and change what.

  • View, create, manage, publish, release, archive, import and delete permissions
  • Across tickets, projects, boards, rules, sprints, clients, incidents, settings, imports and the knowledge base
  • Built-in Admin, Developer and Client roles to start from

Secure account management

Sensible account security out of the box.

  • Email and password sign-in with optional two-factor authentication
  • Password recovery and failed-login protection
  • Active-session visibility and self-service profiles
  • Other sessions signed out automatically after sensitive changes
  • Accounts are created by your administrators: there is no public self-registration

Knowledge and reporting

Internal wiki and knowledge base

Your documentation lives next to the work it describes.

  • Knowledge spaces with nested pages
  • Rich-text editing, attachments and ticket links
  • Version history and restore
  • Per-space permissions

Workspace-wide search

Find anything, including history you imported from Jira.

  • Tickets, descriptions, comments and client conversations
  • Attachment names and wiki content
  • Imported historical data

Reporting and audit trails

Progress and accountability in one place.

  • Burndown, velocity and work breakdowns
  • Delivery metrics and time-in-stage reporting
  • Time against estimate by sprint
  • An audit log you can export to CSV

Migration

Jira migration (free)

Bring your history with you, ticket numbers included.

  • Import through the Jira API or from backup files
  • Keeps ticket numbers and dates, descriptions, comments and changelogs
  • Keeps attachments, sprints, versions, epics, sub-tasks and issue links
  • Keeps labels, components, priorities, custom fields, original authors and timestamps
  • Staging, mapping, dry runs, resumable jobs and progress reporting
  • Repeatable imports without duplicates

Confluence migration (free)

Move your wiki without losing its structure.

  • Import through the Confluence API or from XML space exports
  • Keeps page hierarchy, authorship, dates and rich text
  • Keeps up to 25 recent versions of each page

User experience

A calm, quick interface

Designed to be easy to pick up, for staff and clients.

  • Light and dark themes
  • Responsive layouts
  • Loading placeholders and clear empty states
  • Remembered board positions and predictable browser navigation
  • Recovery screens if something goes wrong
  • Images and video in rich text

Try every feature free for up to 5 users.

Free for up to 5 users

Bring support, delivery and your wiki into one place.

Every feature on every plan. £80 a month for up to 50 users after that, and free migration from Jira and Confluence.