Alba Ticket

The problem

Support tickets and development work are two halves of the same conversation: a customer reports a fault, an engineer fixes it, and the customer wants to know when. Most organisations run that conversation across two products from two vendors, each with its own pricing tiers, and the pieces that make them useful together are sold as add-ons. Teams that must keep their data on their own infrastructure are often left with no current option at all.

What we built

Alba Ticket puts helpdesk and project tracking in one workspace, with nothing held back for a higher tier.

• A customer portal with request types and satisfaction ratings, plus embeddable web forms for customers without accounts.
• Agent queues with SLA tracking for response and resolution times, internal notes and approval workflows.
• Kanban and Scrum boards with WIP limits and swimlanes, ranked backlogs, sprint planning and sprint reports.
• Epics, sub-tasks and versions, with GitHub and GitLab commits and pull requests shown against the ticket.
• Workflows you define, with custom statuses and transitions, and typed custom fields scoped per project.
• Role-based permissions, per-ticket security levels and a full history of every change.
• Live updates across the team without a page refresh, full-text search with keyboard shortcuts, Markdown everywhere and OpenID Connect single sign-on.

Cloud or self-hosted

The same product runs in our cloud or on your own infrastructure. Self-hosted deployments need only PostgreSQL, S3-compatible storage and stateless containers, so they scale horizontally and fit into an existing platform without special treatment. An import tool brings projects and tickets across from Jira Server and Data Center for teams leaving those products.

Why it matters for your project

Alba Ticket is the kind of system we build for clients: real-time collaboration, workflow engines, permissions models, integrations with the tools a team already uses, and a deployment story that works both as a hosted service and inside a customer's own environment. If you need a data-heavy back office or customer portal with those properties, this is a working example of how we approach it.