Ticket destination
Send AI-drafted issues straight to Jira
Turn any feedback topic into a Jira issue with a title, summary, and acceptance criteria drafted by AI from the real notes behind it.
Why connect Jira
- Drafted, not dictated. Title, summary, and acceptance criteria written for you from the feedback.
- Lands where you work. Issues go straight into the Jira project your team already uses.
- Traceable. Every issue is summarized from the notes that prompted it.
Fix CSV export timeouts on large projects
Multiple customers report exports failing on projects above ~10k rows. Summarized from 12 related notes.
Acceptance criteria
- Exports over 10k rows complete without timing out
- Progress is shown while the file builds
- Failures surface a retry, not a silent error
How it works
- 1
Connect Jira
Add your site URL, email, API token, and project key.
- 2
Pick a topic
Choose a ranked feedback topic to ship.
- 3
File the issue
FeedbackFlow drafts and creates the Jira issue in one click.
Prefer the full walkthrough? Read the Jira setup guide.
Before you start
- A Jira Cloud site and an account that can create issues in the target project. Issues are created as that account, so pick one whose name you are happy to see on them.
- Permission to generate an Atlassian API token, which any user can do for their own account at id.atlassian.com.
- The project key of the project you want issues filed into, which is the prefix on its issue IDs.
How to connect Jira to FeedbackFlow
- 1
Enter your site URL and account email
Add your Jira site URL, in the form https://yourorg.atlassian.net, and the email of the account that will create the issues. That account needs create-issue permission in the target project, because everything FeedbackFlow files is attributed to it.
- 2
Create and paste an API token
Go to id.atlassian.com, then Security, then API tokens, and create a token. Paste it into the Jira card in FeedbackFlow. Atlassian shows the token once, so copy it immediately. FeedbackFlow stores it encrypted and uses it only to authenticate issue creation against your site.
- 3
Set the project key
Enter the key of the project you want issues filed into. It is the prefix on that project's issue IDs, so a project whose issues read WEB-123 has the key WEB. Get this wrong and issue creation fails with a clear error rather than filing into the wrong place.
- 4
File your first issue
Open a ranked topic and choose to create a Jira issue. FeedbackFlow drafts a title, a summary, and acceptance criteria from the feedback behind that topic, shows you the draft, and creates it in your project on confirmation.
The exact Request URL and any values you need to paste are shown on the Jira card inside your project settings, because they are specific to your project. Full Jira setup guide.
What FeedbackFlow writes to Jira
A single issue per topic you choose to file, with the fields below. Nothing is created automatically and nothing already in Jira is modified.
| Field | What it contains |
|---|---|
| Issue summary | A title drafted from the topic, written as a problem statement rather than a restatement of one customer quote |
| Description | A summary of the underlying feedback items, so a reader sees the pattern rather than a single report |
| Acceptance criteria | Drafted from what customers actually described as broken or missing |
| Project | The project matching the key you configured; issues are never filed anywhere else |
What this looks like in practice
A topic reaches the top of your ranked list
You open it, see the twelve pieces of feedback behind it and who sent them, and decide it is worth building.
You click through to file it
FeedbackFlow drafts a Jira issue from those twelve items: a title, a description explaining the pattern, and acceptance criteria drawn from the specific failures customers described.
Engineering picks it up in the next sprint
The issue arrives in the project they already work from, with enough context that nobody has to go back and ask what the customer meant.
Limits worth knowing
What this connector does not do, so you can find out here rather than after you have wired it up.
- Issues are created, not kept in sync. Closing the Jira issue does not change the topic in FeedbackFlow, and editing the issue in Jira does not flow back.
- One issue per topic, filed on demand. There is no rule engine that files issues automatically when a topic crosses a threshold.
- A single project key per connection, so feedback cannot be routed to different Jira projects based on its content.
- Jira Cloud only. Server and Data Center instances are not supported by this connector.
Frequently asked questions
- Does FeedbackFlow create Jira issues automatically?
- No. Every issue is created because you chose to file that topic. AI does the drafting, not the deciding: it ranks topics and writes the issue content, and you decide which ones become work. That is deliberate, because automatically filing issues from customer feedback is how a backlog fills with things nobody triaged.
- What does the drafted issue actually contain?
- A summary line written as a problem statement, a description that synthesizes all the feedback items behind the topic rather than quoting one of them, and acceptance criteria drawn from what customers described as broken or missing. The point is that an engineer can pick it up without going back to the source conversations, though the underlying items stay linked in FeedbackFlow if they want them.
- Which account are issues created as?
- The account whose email and API token you configured. Jira attributes created issues to that account, so it shows as the reporter. Teams that want the provenance obvious often use a dedicated integration user rather than a person, so it is clear at a glance which issues came from feedback triage.
- How is the API token stored?
- Encrypted at rest with AES-256-GCM, and used only to authenticate issue creation against the site you configured. It is never returned to the browser after you save it. If you rotate or revoke the token in Atlassian, issue creation stops working until you paste in a new one, which is the expected behaviour.
- Can I file to more than one Jira project?
- Not from a single connection. One project key is configured per connection, and every issue goes there. If different feedback needs to reach different projects, the practical approach today is to file into one project and route from there using Jira's own automation, which is better at that job than a feedback tool would be.
Connect Jira today
Free plan. No credit card. Live in 2 minutes.