Integrations
Connecting to Linear
Read issues and projects, file work, and answer what is actually in flight.
Connect Linear and Gini can read and manage your issues and projects: find work, file it, update it, and turn a conversation into a tracked ticket without anyone leaving the channel.
What it can do
- Find issues and projects. "What's assigned to me?" or "show open bugs in the mobile project."
- Read the detail. Description, comments, status, labels, sub-issues.
- File issues. Title, description, assignee, priority, labels, project.
- Update issues. Change status, reassign, set priority, add labels.
- Comment. Drop an update or a note on an issue.
- Browse the workspace. Teams, projects, workflow states, members.
How to connect
Open Integrations
app.ginicomputer.com → Integrations, find Linear, and click connect.
Authorise in Linear
Sign in when Linear prompts you. That screen is the real contract, so read what it grants.
Come back
Gini can now search, file and update issues. Nothing else to configure.
Gini asks for read and write access to your Linear workspace. You can revoke it from Linear's own settings at any time, or from Integrations.
What changes anything
Reads are free. Anything in the second group changes your team's board, so read what Gini tells you it did and follow the link.
| Operation | What it does | Changes anything? |
|---|---|---|
| Search issues | Find issues by filter | No |
| Get issue | Read one issue in full | No |
| List teams and projects | See what exists | No |
| List workflow states | See the statuses in use | No |
| Create issue | File new work | Yes |
| Update issue | Status, assignee, priority, labels | Yes |
| Add comment | Post on an issue | Yes |
What it's great for
- Filing fast. "Create a Linear issue: checkout crashes on Safari, high priority, assign to Sam."
- Turning a thread into tickets. Take the decision made in a channel and file the three things that follow from it, each carrying the conversation as context.
- Triage. "Summarise everything assigned to me that's still open, worst first."
- Standup without the standup. What moved, what did not, what is blocked and on whom.
- The weekly update. "Write the eng update from what closed this week." Engineers can read the issue list themselves. What costs them time is writing the version their VP will read.
Example routine
Turning every customer escalation into tracked work, every morning:
- Read yesterday's escalations from the support channel.
- Check whether an issue already exists for each, and skip the duplicates.
- File the rest in the right team, with the customer thread in the description.
- Post the list in the channel, with links.
Ask for it by hand a few times first, then let Gini offer to take it over. See Routines.
Good to know
- It works within your Linear access. Gini sees the teams, projects and issues your own account can. See How connections work.
- Be specific when filing. Naming the team, project, priority or assignee is what makes an issue land correctly the first time.
- Say "list them first" if you would rather check. Filing is reversible, so Gini files and links rather than stopping. On a busy board that is usually right; when it isn't, ask for the list.
- Include the context. When filing from a thread, ask Gini to fold the thread into the description. An issue with no context costs someone twenty minutes later.
Pair it with GitHub
GitHub connects read-only, so Gini cannot file anything there. Together they give you the direction you actually want: read the code and the PRs in GitHub, track the work in Linear.
Troubleshooting
Gini can't see a team or project
Check that your own Linear account can see it. Gini works with your access, so a team you are not a member of is invisible to it too. If your account does have access, reconnect from Integrations.
Filing an issue fails
Usually one of three things: you lack permission to create issues in that team, a required field (title, team) was not clear from the ask, or the workflow state named does not exist in that team. Gini says which.
It filed into the wrong project
Name the project in the ask. Where a team runs several, "file it in Linear" leaves Gini to guess from context, and it will guess from the channel.