Jira is where your team already triages, prioritizes and fixes problems. So when users report a bug or suggest an improvement, that’s where their feedback should land, not in a separate dashboard someone has to copy from.
How it works: add the Saber Feedback button to your website or web app, connect it to your Jira project, and every feedback report becomes a new Jira issue. Each issue includes the user’s message, their screenshot, the page they were on, and their browser and device details. Your users don’t need a Jira account.
- Set up the Jira integration in three steps
- What each Jira issue includes
- Saber Feedback vs Jira’s Issue Collector
- Ask for the feedback your team needs
- Frequently asked questions
Set up the Jira integration in three steps
1. Add the feedback button to your site
Sign up for a 30-day free trial, create a feedback form, and paste the code snippet into your website. It takes a few minutes, and there are plugins and guides for WordPress, Shopify and other platforms. Our guide on how to add a feedback button to your website walks through it.
2. Connect your Jira account
In the Saber Feedback app, open Third-party Integrations, click Setup New Integration and choose Jira. Enter your Jira address (for Jira Cloud, this ends in .atlassian.net) then the username and an API token for the Jira user Saber Feedback should create issues as. We recommend a dedicated user for this.
Then choose the Jira project and issue type for new reports, such as Bug or Task, and set the issue title. You can include a summary of the user’s message in the title automatically.
3. Send a test report
Click Test Settings to send a sample report to Jira and check it arrives as expected, then save. From then on, every feedback report from your site creates a new issue in that project.
The Jira integration help doc has every setting in detail.
What each Jira issue includes
Saber Feedback collects the information your team needs to understand and fix a problem, so nobody has to go back to the user to ask which page, which browser, or what they saw. Each Jira issue can include:
- The user’s message
- Any screenshot they attached
- Any category or rating they chose, if your form includes them
- The page URL
- The user’s browser, browser plugins, operating system and device
- The user’s location and IP address
- The user’s email address, if they gave it or you passed it in from your app
- When the feedback was submitted
- JavaScript events, including errors, from before the report was sent
Your developers get the detail they need to reproduce a bug. Your product managers can see exactly which page a problem is on. Your support team can see how the user felt about the experience. And because it all arrives in Jira, you can assign, prioritize and track it like any other issue.
Christopher Roberts, learner success manager at AICPA, the world’s largest member association representing the accounting profession, says:
Saber Feedback has definitely made our lives easier. It doesn’t take them more than a couple of seconds for students to give feedback, and it’s simple for us collecting that feedback in Jira.
Saber Feedback vs Jira’s Issue Collector
Jira’s built-in Issue Collector also puts a feedback form on your website. It’s free, and if all you need is a basic text form on a company-managed project, it may be enough. Saber Feedback is for teams that need more from each report.
| Jira Issue Collector | Saber Feedback | |
|---|---|---|
| Works with team-managed Jira projects | No, company-managed only | Yes |
| Screenshot of the page | No | Yes, taken from the feedback form |
| Browser, device and page details | Basic | Detailed, plus JavaScript events |
| Custom forms | Limited | 14 field types, with logic between questions |
| Different forms on different pages | Yes, one collector per form | Yes |
| Button styling and languages | Limited | Custom label, color, position and language |
| Send feedback elsewhere too | Jira only | Jira plus email, Slack, Zendesk and more |
| Price | Included with Jira | From $99/month, on plans with screenshots and integrations |
Ask for the feedback your team needs
Forms can be as simple or detailed as you like. Choose from 14 field types, including text boxes, dropdowns, checkboxes, and star and emoji ratings, and show follow-up questions based on earlier answers. You can use different forms on different parts of your site: a bug report form in your app, and a content feedback form on your help pages.
You can style the feedback button to match your site, or open the form from your own link or icon. Here, Kantar uses a question mark icon to open its customized form:
Frequently asked questions
Do my users need a Jira account?
No. Users fill in the Saber Feedback form on your site, and Saber Feedback creates the Jira issue using the Jira account you connect. Your users never see Jira.
Does it work with self-hosted Jira?
Yes. Saber Feedback works with Jira Cloud and with self-hosted Jira Server. On a self-hosted server you need to turn on attachments so screenshots can be added to issues; the help doc shows how.
Can feedback go to other tools as well?
Yes. Saber Feedback also integrates with GitHub, GitLab, Bitbucket, Trello, Asana, Basecamp, Redmine, Zendesk, Slack and Zapier, and can send feedback by email or webhook. See all integrations.
Where can I use the feedback button?
On almost any website or web app, including staging and test sites, customer portals, WordPress and Shopify sites, and most learning management systems.
Try Saber Feedback with Jira free for 30 days
Set up a feedback button that sends complete, actionable reports straight to Jira. No credit card required.