01 — Overview
Jira is where engineering work is tracked, and it’s rarely where other teams want to request it or follow it. Chamfer lets you build the screens in between: an intake form for operations requests, a release board that finance can read, a cross-project report for leaders who don’t work in Jira every day. Requests arrive as well-formed issues with the right type and fields, so engineering spends less time triaging.
Describe the tool and the Bench reads your projects, issue types, workflows and custom fields, then writes the JQL and the updates. Transitions can require a Sign-off, such as moving a change to Released, and the app adds a comment to the issue naming who approved it. People who only read reports see them in Chamfer, limited by their app role. Jira Cloud and Data Center both connect, and custom fields and workflows carry over as they are.
02 — What you can do
JQL from a sentence
Describe the issues you want and the Bench writes the JQL, which you can edit.
Gated transitions
Require a named approver before an issue moves to a status like Released.
Requests from anyone
Intake forms create issues with the right type, fields and project every time.
03 — FAQ
Before you connect Jira
Does Chamfer support Jira Data Center?
Can transitions require approval?
Will our custom fields and workflows work?
Can we combine Jira with GitHub data?
04 — Pairs well with
