CURRENT PILOT
Pricing by scope
The proposal accounts for your repositories, expected usage and setup requirements. The price is agreed in writing.
Pilot pricing
See the product. Then define your pilot.
Start with a demonstration of the Jira ticket generator. If it fits your team, agree on the pilot scope, conditions and price before connecting your environment.
What shapes the proposal
A scope that matches your environment.
Repository scope
The number, size and structure of the repositories included in the pilot.
Expected usage
How often your team expects to turn descriptions into Jira tickets.
Setup requirements
Your Jira configuration, repository access and data-handling requirements.
Getting started
From demo to pilot in three steps.
- 01
See the ticket generator
Walk through a request, the code context and the generated ticket using demonstration data.
- 02
Agree on the pilot
Define the Jira project, repositories, conditions, access requirements and price in writing.
- 03
Evaluate it with your team
Use requests from your backlog to assess ticket quality, code context and the review effort.
See the Jira ticket generator in action
Bring a description. See the ticket.
Walk through the app inside Jira, from a request to a generated ticket, using a demonstration repository.
30-minute product demoSample data. No repository connection needed.
Send a request and we will contact you to arrange the demo.