Linear, GitHub, Jira and Slack

Integrations carry client feedback from Lyba into your team's own tools. Linear, GitHub and Jira receive issues your studio has confirmed. Slack receives notifications about review activity. Your client never sees any of this: integrations only extend the studio side of the review.

Connect an integration

Integrations are set up per project, in Dashboard → Settings → Integrations.

1. Open Dashboard → Settings → Integrations.
2. Select the project.
3. Click the connect button on the tool's card: Connect Linear, Connect GitHub, Connect Jira or Add to Slack.
4. Approve Lyba's access on the tool's own sign-in page. You come back to Lyba when it's done.

Every connection goes through the tool's own authorization, so there are no API keys or tokens to paste. Stored credentials are encrypted.

Only studio owners and admins can connect, change or disconnect an integration. Every member of the studio can review issue drafts.

Linear

Click Connect Linear and authorize Lyba in Linear. If your Linear workspace has more than one team, pick the team that should receive issues. Confirmed drafts and comments then become issues in that team.

GitHub

GitHub Issues is available for React projects. Lyba binds the connection to the repository the React project already belongs to: its project key must be owner/repo, which the Lyba CLI normally sets from the repository it runs in on GitHub Actions. You never choose a repository during authorization.

1. Check that the GitHub card shows the repository you expect.
2. Click Connect GitHub.
3. Review the access GitHub asks for, and authorize.
4. Back in Lyba, the card shows the verified repository as connected.

GitHub asks for the repo scope. GitHub OAuth Apps bundle issue creation in private repositories into that scope, which also grants code access. Lyba only reads repository metadata and creates issues.

Connecting fails if the repository is archived, if GitHub Issues is turned off for it, or if your GitHub account can't see it.

Jira Cloud

Lyba supports Jira Cloud. Jira Data Center and Jira Server aren't supported.

1. Click Connect Jira and authorize Lyba with Atlassian.
2. Choose the site, the project and the issue type that should receive issues. Lyba only lists projects where you can create issues, and it leaves out subtask types.
3. Finish the setup within 15 minutes of authorizing, or start again.

The issue type you choose needs a Description field. If it has required fields that Lyba can't fill in, give those fields a default in Jira, or choose another issue type; the setup explains which fields need attention.

Slack

Click Add to Slack and authorize Lyba. Notifications go to the channel shown on the Slack card, and each one carries a Review in Lyba link back to the review.

Choose which events to be notified about, then click Save preferences:

• New issue drafts
• New comments and replies
• Resolved feedback
• Client sign-offs
• Studio-approved issues

Unticking every event pauses notifications without removing the Slack connection.

Turn feedback into issues

Nothing is created in Linear, GitHub or Jira automatically. A comment can be a question, repeat an earlier request, or conflict with the agreed scope, so an issue is only created when someone in your studio confirms it.

Review issue drafts

When Lyba drafts an issue from client feedback, the draft appears in the session's Studio review area, filed under Needs review, Approved or Dismissed. Each draft shows the original comment where available, the suggested issue text and labels, and any conflict with an earlier client sign-off.

1. Click Review draft to open the draft and edit its text.
2. If more than one tracker is connected, choose where the issue goes. Lyba never quietly sends it to a different tracker instead.
3. Click Approve & create. The button names the tracker you chose, for example Approve & create in Linear.

Created issues stay under Approved with a link to the issue, who reviewed it and when. Dismissed drafts stay visible as history.

Send a single comment

You can also push one comment straight to your tracker with Create issue on the comment in the dashboard. The issue includes the comment, the reviewer and a link back to the review in Lyba, and the comment then links to the issue it created. If more than one tracker is connected, Create issue uses GitHub first, then Linear, then Jira.

What creating an issue doesn't do

Creating an issue doesn't resolve the comment, approve the session, or change your client's approval record. Client sign-off and studio issue approval are separate decisions.

If Lyba can't confirm whether an issue was created, the draft shows Check delivery instead of retrying on its own. Check your tracker before trying again in Lyba, so you don't end up with a duplicate issue.

Check or disconnect a connection

• Check connection tests a Linear, GitHub or Jira connection without creating anything.
• Send test message posts a test message to your Slack channel.
• Disconnect removes that project's saved connection. Issues already created stay in your tracker, and drafts stay in Lyba.

Disconnecting in Lyba doesn't withdraw the authorization you gave the tool itself. To do that, also remove Lyba from the tool's authorized apps, for example GitHub Settings → Applications → Authorized OAuth Apps, or your connected apps in Atlassian.