> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.feedbucket.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Feedbucket and Linear integration

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

# **Video Tutorial**

${youtube}[](nSYs9XjjeJ4)


# Install the Linear 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 Linear as show in the image below.
![](https://storage.crisp.chat/users/helpdesk/website/-/4/c/1/c/4c1cdabe55cf0c00/linear-1_1h7tfej.png)

3. If this is the first time you are connecting Feedbucket and Linear, a pop-up will appear where you have to allow the connection between Feedbucket and Linear. Select your team and click on the Authorize button.

||| __Admin scope is now required__ in order to create webhooks. If you don't allow the admin scope, Feedbucket can not add webhooks to complete the 2-way sync.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/c/1/c/4c1cdabe55cf0c00/linear-2_vlissa.png)
4. You will now see a green bar on the Linear 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 Linear connection for this project.


# Configure the Linear 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 Linear 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 Team. If you only allowed one Team when connecting Feedbucket there should only be one value here.
2. Select the project. You can search in the textfield for your project to more easily find it.

|| If you set the project as "No project (Team level)", Feedbucket will create new issues under your team. If you instead select a project, the issue will be created as part of that project.

3. Select what state Feedbucket should create new issues in. Basically, this means that when Feedbucket creates a new issue in Linear, it will have this state.
4. The resolve state is probably the only thing that might be a bit confusing. This is the state that Feedbucket should associate with a feedback being resolved. If feedback is resolved in Feedbucket, we will change the issue to this state. If an issue is moved to this state inside of Linear, we will resolve the feedback in Feedbucket.
5. Optionally, you can select labels that the issue will be created with.
6. Click on `Advanced Settings` top open up more settings.
7. Configure Feedbucket to set a Milestone on each issue it creates. You need to select a project before Milestones becomes available.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/c/1/c/4c1cdabe55cf0c00/linear-3_1k9u8ds.png)


# How to use the Linear 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 Linear. This issue will be placed in the project that you selected in step #2 above and have the state that you selected in step #3 above. 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 have selected any Labels in #5 or Milestone in #7 it will also automatically be set on the newly created issue in Linear.

|| Note that the issue will be created with the Linear account that you connected Feedbucket and Linear with in step #3 during installation.


### 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 Linear by Feedbucket, that comment will also be created inside of Linear under the correct issue. That way, all comments that happens in Feedbucket will automatically be pushed to Linear as well.

![Comments created in Feedbucket is automatically pushed to Linear as well.](https://storage.crisp.chat/users/helpdesk/website/-/4/c/1/c/4c1cdabe55cf0c00/linearcomment_1k5pgir.png)

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 Linear. 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 Linear.

| When the comment is sent, you should see an acknowledgement appearing under it that confirms that Feebucket received the comment successfully via webhooks. It will appear as a new reply comment and look like this: *"✅ Feedbucket received the comment starting with: 'the actual comment' + timestamp"*. You should see it appearing within a few seconds, please make sure to refresh the page if you don't.

|| When using the at (@) symbol in Linear it will think you want to mention someone inside of Linear or a specific issue. 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 change state to what you configured in step #4.

Again, there is a 2-way integration here as well. If the issue is moved to the state selected in #4 in the configuration, it will resolve the feedback in Feedbucket.

If the issue in Linear is moved to any state that is of type `Canceled`, we will also resolve it in Feedbucket (for example `Duplicate` or `Canceled`).


### When the feedback is re-opened

If the feedback gets re-opened from Feedbucket the issue will change state to the `Open state` that you configured in step #3.

There's a 2-way sync here as well. If you change the issue from the state in step #4 to something else, it will be unresolved again in Feedbucket.


# FAQ

**What permissions are required to integrate with Linear?**
Admin permissions are required to the Linear project that you want to connect with.

**Why do I need Admin scope to connect with Feedbucket?**
To be able to create webhooks we need the admin scope. If we can't create webhooks we can not act on changes happening inside of Linear. Therefore, without webhooks the 2-way sync can't work.


# How to disconnect the Linear integration

When the Linear integration is active you will see a button for `Disconnect`. Click this to disconnect your Linear integration with this project.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/c/1/c/4c1cdabe55cf0c00/linear-4_35zllf.png)