<style> .nav__links { display: block !important; overflow-x: auto; } .nav__menu, .nav__k { display: none !important; } </style>

← All projects

Project and ticket tracking · 2026

Ivy Tickets

An application for running projects and tickets: linked tickets, deployment planning, work logs and reports, with project-level permissions.

Ivy Tickets dashboard with ticket statistics and recent activity
Year
2026
Client / industry
Own product
Role
Design, architecture, full-stack, deployment
Status
Live, sign-in required
Stack
  • Angular 22
  • Angular Material
  • NestJS 11
  • TypeORM
  • SQLite / Oracle
  • Nginx
  • Cloudflare

Open the app (account required)

Challenge

Tickets, deployment planning and time tracking in one place — with status-transition rules enforced by the server, not by the interface.

Solution

An npm-workspaces monorepo: Angular with lazy-loaded feature modules, NestJS as a modular monolith and shared contract types. The database is chosen by configuration — SQLite in WAL mode or Oracle, with separate migrations for both. The status workflow has required fields per transition, and automations run only after the transaction commits.

Outcome

The application runs at tickets.matqode.com on a VPS behind Cloudflare. Accounts are self-service, with e-mail confirmation.

What I built

  • Tickets with links, comments, attachments and work logs
  • JQL-style advanced search, saved filters and scheduled digests
  • Global and per-project workflow plus automation rules (status change, merged pull request, passed due date and more)
  • Deployment window planning (MTP) and reports with change-request analytics
  • Roles and permissions, e-mail account confirmation, notifications
  • GitHub and Jenkins integrations
  • Load-test scenarios for 100 and 200 users

Local time · Warsaw

Angular · GSAP · Lenis · no trackers

Back to top ↑