Articles on: Integrations

Feedbucket and Jira integration

Feedbucket can deeply integrate with Jira. That means that your team should be able to manage all feedback inside of Jira instead of in the Feedbucket Admin.


Video Tutorial




Install the Jira integration on your Feedbucket project


  1. Go to your project and then click the tab Integrations.
  2. On the integrations page click the button Connect next to Jira as show in the image below.


  1. If this is the first time you are connecting Feedbucket and Jira you will be redirected to Jira where you have to allow Feedbucket. Check the permissions and click on the Accept button as shown in the screenshot below. Once the connection between Feedbucket and Jira has been established you will be redirected back to Feedbucket.


  1. You will now see a green bar on the Jira integration that indicates that the connection is made. The settings should have opened automatically but in case it doesn't, click on the Settings button to start configuring the Jira connection for this project.



Configure the Jira integration to your needs


Most often, you will create one Feedbucket project per client website you are building. That way you can connect each project to a specific project inside of Jira as well. It's up to you how you want to configure it.


After you connect you should see the configuration pop-up. If you don't, just click on the Open Settings button.


  1. Select the site. If you only allowed one site when connecting Feedbucket (Step #3 under Connecting the integration) there should only be one value here.
  2. Select the project where you want Feedbucket to add new issues to. After selecting a project, Feedbucket will load in some additional resources.
  3. Select issue type. What type of issue should Feedbucket use when new feedback is created?


A good idea could be to create a new Issue-Type specifically for Feedbucket. If you use an existing issue-type, make sure that it has no required fields like build, stage, etc that Feedbucket can't fill.


  1. What status should be counted as Done? This means that if you resolve the issue in Feedbucket, the issue in Jira will get this status. It also means that when you set this status in Jira, the feedback will be resolved in Feedbucket.


At the moment, Feedbucket can only assign one status in Jira as the resolved-status.


  1. Feedbucket can sync tags with Jira. This means that the tags that you set in Feedbucket when creating the feedback will also be set on the Jira issue. Update the tags later on and Feedbucket will keep this tag in sync between Feedbucket and Jira. Read more about it under Using the integration.
  2. Set a parent issue for feedback from Feedbucket. If the selected Issue Type is a Sub-task, all non-subtask issues will be available as potential parents. For non-subtask Issue Types, only Epics will be shown as possible parent issues. Feedback will be created as child issues under the selected parent.




How to use the Jira integration


Once you have configured everything as you wish, below is how the integration should behave.


When new feedback is created


Whenever a new piece of feedback is created in Feedbucket, an issue will be created inside of Jira. This issue will be placed in the project that you selected in step #2 above and be of the issueType that you selected in #3. The issue will automatically have all of the technical details that Feedbucket collected like the session information of the reporter, the screenshot/recording etc.


if you set a label in #5 that will automatically be added to the issue as well. In case you are using a parent task, the new issue will be created as a sub-task under that parent task.


Note that the issue created in Feedbucket will be created by the account that you configured Feedbucket and Jira with in step #3 of the Installation above.



When a new comment is created on feedback


A piece of feedback can have lots of comments as a thread to communicate and collaborate. When a new comment is created on a piece of feedback that has been created in Jira by Feedbucket, that comment will also be created inside of Jira under the correct issue. That way, all comments that happens in Feedbucket will automatically be pushed to Jira as well.


Comments created in Feedbucket will automatically be attached to the Jira issue


As you can see in the image the real power lies in the two-way communication here. If your team needs to ask a follow-up question that can be done without leaving Jira. All you have to do is to add a new comment that starts with @feedbucket and it will automatically be pushed over to Feedbucket and notify the client of this new comment from you. Regular comments submitted without the prefix of feedbucket will not sync over so you can continue to keep your internal conversations flowing in Jira.


When using the at (@) symbol in Jira it will think you want to mention someone inside of Jira. You should just write the @feedbucket as regular text and not click in the mention drop down.



When the feedback is resolved


If the feedback gets resolved from Feedbucket, the issue will automatically get the resolve status that you selected in #4 in configuration


Again, there is a 2-way integration here as well. If your team has completed the feedback they set the status of the issue to the resolve status and it will automatically resolve in Feedbucket. This way your team can manage all aspects of the feedback without leaving Jira.



When the feedback gets re-opened


Since Jira can have very complex workflows we are not able right now to handle re-open. If you re-open a feedback in Feedbucket, you need to manually update the issue to the correct status in your flow. If you need to open a feedback from Jira, you need to go to Feedbucket and re-open the feedback as well.


We are doing this because we have seen a lot of errors when we tried to re-open an issue automatically. Imagine if you have two columns called Done -> Client Approved. When you move it out of Done to Client Approve Feedbucket might think you want to re-open the feedback since it's not in the Done column anymore.



How to sync tags between Feedbucket and Jira


Feedbucket can keep tags in sync with Jira. To know more about how to set this up you can view the documentation of tags.


This work with Labels in Jira. So they are called tags in Feedbucket but it's the native Label in Jira we can sync with.


In essence it means this:


  1. If you add a tag to a piece of feedback in Feedbucket that is set to sync with Jira, Feedbucket will update the Jira issue and set the corresponding label. If you remove a tag in Feedbucket, the label will be removed in Jira.
  2. If you add a label to the issue in Jira, the feedback in Feedbucket will also get this tag if it's set up to sync.



Disconnect


When the Jira integration is active you will see a button for Disconnect. Click this to disconnect your Jira integration.






Updated on: 12/01/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!