GitHub & deployments
Link GitHub commits and pull requests to tickets automatically, show CI status, and record every deployment with its environment, version and tickets.
| Environment | Version | Status | Included | When |
|---|---|---|---|---|
| Production | v2.4.1 | Succeeded | 6 tickets | Today 14:22 |
| Staging | v2.4.1 | Succeeded | 6 tickets | Today 12:10 |
| Production | v2.4.0 | Rolled back | 4 tickets | Mon 09:55 |
| Staging | v2.4.0-rc2 | Failed | 4 tickets | Fri 16:31 |
PR #318 feat: PO number on invoice export Merged CI passing
Quick answer
Connect a project to its GitHub repository and Jonta links any commit or pull request that mentions a ticket key. Tickets show PR and CI status, can move automatically when a PR opens or merges, and every deployment records the environment, version, commit and the tickets it contained.
Commits and pull requests appear on the ticket automatically.
Know what shipped, where and when.
Included on every plan: Free, Pro and Enterprise. See pricing.
Mention the ticket key (for example NW-142) in a commit message, branch or pull request, and Jonta links it to that ticket automatically.
Yes. Deployments can be reported automatically by your CI pipeline or recorded manually, with states for started, succeeded, failed and rolled back.
Jonta currently integrates with GitHub. Deployments can be reported from any CI system that can call Jonta.
Try every feature free for up to 5 users.
Free for up to 5 users
Every feature on every plan. £80 a month for up to 50 users after that, and free migration from Jira and Confluence.