linear/linear-zapier

Linear's Zapier integration

Linear API

The issue tracking tool you'll enjoy using

Linear helps streamline software projects, sprints, tasks, and
bug tracking. It's built for high-performance teams.

⚠️ Monorepo Readme

If you are looking for documentation on the Linear SDK or Linear API visit developers.linear.app instead.

The Linear Client uses custom GraphQL Code Generator plugins to produce a typed SDK for all operations and models exposed by the Linear production API.

Structure

This monorepo uses yarn workspaces and lerna to publish packages.

Generated code uses file prefix _generated and should never be manually updated.

Open source packages:

• sdk - The Linear Client SDK for interacting with the Linear GraphQL API
• import - Import tooling for uploading from other systems
• codegen-doc - GraphQL codegen plugin to generate GraphQL fragments and documents
• codegen-sdk - GraphQL codegen plugin to generate Typescript SDK from fragments and documents
• codegen-test - GraphQL codegen plugin to generate a jest test for the Typescript SDK

Get Started

# install dependencies
yarn

# link package dependencies
yarn bootstrap

# build all packages
yarn build

# test all packages
yarn test

# update the schema from the production API
yarn schema

# create changeset for generating CHANGELOG.md
yarn changeset

Plugin Flow

1. The @linear/codegen-doc plugin is used by codegen.doc.yml to generate fragments and documents
2. The @linear/codegen-sdk plugin is used by codegen.sdk.yml to generate the typed Linear SDK
3. The @linear/codegen-test plugin is used by codegen.test.yml to generate a typed jest test

License

Licensed under the MIT License.

linear-zapier's Issues

[Feature Request] Ability to set a due date

It would be helpful to set due dates in order to meet deadlines as well as help the assignee and their team meet internal and external SLAs.

Currently, we've been calculating deadlines using Zapier's internal Formatter: Date/Time event. Then we include that deadline variable at the top of issue descriptions to help the assignee notice them.

Please let me know if you have any questions.

No project appears in Create Issue Linear Action

I have a project in my linear team and it doesn't appear here

Example feature request

This is an issue on the https://github.com/linear/linear-zapier repo.

[Feature Request] Ability to grab latest comment

I have no idea if I am doing this right, but I am hoping to have the Zapier integration updated so that one of the fields that I can pull data from is the latest comment on a ticket.

My use case here is if I update a ticket in Linear via a new comment, I want to be grab that comment and (via Zapier) add it to a database entry in Notion.

Quinn test 2

Test @tommoor #54

• one
• two
  [ ] 1

codetest

Heading

Uploading choosy_2.3.1.zip…

this is an after the fact edit

[Feature Request] Retrieve Labels in Payload

It would be great if the returned issue data had labels attached, just like how the webhook currently provides it.

[Feature Request] Sub-Issue Separation

It would be really helpful for Linear to show if something is a sub-issue or not.

Regression: Creator & Project fields no longer set for new tickets

We have a couple of Zaps - One that sends a message to chat when a new ticket is created, and another that sends one when a ticket is updated.

During a previous update to the Zapier integration, we lost the "Creator" and "Project" fields for new ticket notifications; they're always blank now, including when the sample data is fetched during Zap setup:

I can't see any other fields that contain the same data; perhaps i'm missing something?

Regression: "Updated Issue in Linear" trigger no longer contains issue status

Last week, Zapier required us to update the deprecated "Linear for version 2.1.3" app to the newer version "Linear Beta". We're using the app to automatically create tickets and send an update on Slack whenever their status changes. However, after changing to the new version, it seems that the status field no longer exists in the trigger response. This unfortunately means that the status change monitoring is broken.

Is this an intended change, or is there a workaround?

Feature Request: Ability to GET an existing Linear Issue

This is super cool. Could you add functionality to GET properties of an existing Linear issue? My thoughts are that the issue ID could be passed in and I'd like to get back the details of the issue and eventually trigger an event in another application anytime a comment is made on the Linear issue.

Quinn test

Test issrewruer rewrewrewrewrewrewrggregerergg

rewr	rewr	rewr	reewr	rr	rrwer
rewrwer	rewr	wer	werwe	ewrwe		gergreger
wer					erger
rewr	wre		gre	ggerg	rg
rew	gergerg	gregreger	erger	erg	gerg	r

rrwerewrewr rewrewrwerer erfgregewrfegrebergger

[Feature Request] Ability to get "previous" data

Using the "Issue Updated" trigger in Zapier, it would be great to be able to access the previous values of the data fields. This would allow more in-depth Zapier usages.

From my understanding, this kind of data is already provided by Linear Webhooks.