Jira delivered issues
One search per page over the issues your query matches, and three fields on each: when it resolved, its project and its resolution. Never a description, never a comment, never an attachment.
Access
- Kind
- A read-only key you paste
- What to give
- Site, email and API token
- Why that one
- An Atlassian API token that can browse the projects you want counted. This source writes no spend: it reports what the spend produced.
What it attributes on its own
- From the source
- issues resolved per day · the project and the resolution each carried · the query you chose to count them by
- Needs a rule or a trace
- which issues an assistant helped with — Jira records no such thing, so cost per delivered issue is a floor on the cost per assisted one · the workflow, which you tell us · how large an issue was: an epic and a typo both count as one
Connecting it
- Create an API token. Create API token, name it so you recognise it later. It carries your own browse permissions and nothing more. Open ↗
- Decide what counts as delivered. Left empty, every resolved issue counts — including ones resolved as Won't Do. A condition like resolution = Done, or project = SUP AND resolution = Done, is usually what a team means.
- Name the workflow, paste the three values, click Test and connect. Valistry runs the query over the last seven days, reports how many it found, then fills thirty.
Where your assistants write the issue key into a trace, we can join issue to spend exactly instead of by workflow; ask us and we will read it.