Before connecting an Outcome to Linear in Elate, it’s best to first decipher whether or not you’d like to pull in Linear data to a Tactic or an Outcome. The answer may not be what you think!
An Outcome in Elate will allow you to create powerfully custom configurations, but is most useful if you’re interested in the generic state of your Linear instance, not tracking the progress of specific Projects or Initiatives. (Think: tracking the number of Issues created, number of high priority issues deployed instead of "how are we tracking towards the Product Launch?").
If you are hoping to track the progress of a certain Project or Initiative in Linear (such as a bigger feature release, task, or team-wide project), using Tactics would be the way to go. Learn more about how to connect Linear to your Tactics here.
Now, let's learn how to connect your Outcome to Linear. Be sure you've already connected Linear to your Elate account.
First, go to the outcome you would like to connect to Linear. Select “Connect” and then “Linear” from the connect modal. You can connect Linear by going to your Integrations Library and selecting "Connect" under the Available tab.
Next, go to the outcome you would like to connect to Linear. Select “Connect” and then “Linear” from the connect modal.
From there, you will have the option to configure your Integration as shown below.
“Resource” refers to the data you will be pulling from.
In many cases, you will want to select “Collections” as the Resource. Collections includes both Projects and Cycles in Linear. You will have the option to filter by Collection type later on, but it will often serve as a good starting point for your data.
“Tickets” refers to Issues in Elate. Tickets will be helpful if you are interested in tracking the number of issues created, completed, etc. Please note that if you are wanting to track the progress of a specific project or initiative in Linear, this should be done by configuring a Tactic Integration.
Accounts, Attachments, Comments, Contacts, Tags, Teams, and Users should all correspond directly to their Linear fields.
Beyond selecting a Resource, the configuration screen allows you to fully customize how you group and filter your data from Linear.
If you are hoping to filter by a specific Project, Cycle, etc., first choose “Collections” as your Resource, and fill out your other desired fields. Once completed choose "Add Filter" in the bottom right and filter by "Collection Type". This will allow you to filter by unique Projects, Cycles, etc.
Let's walk through an example together!
In the below example, I am interested in seeing how many Linear issues Lindsay Webb has created in the Quarter. I selected “Tickets” as my resource, chose “Created At” at the time field, and chose to group my data by the Creator of the Tickets. Then, I added a filter in the bottom right to only see Tickets that Lindsay created.
In the below example, I am interested in seeing how many Linear Issues were successfully deployed. I chose to pull from “Tickets” and wanted to refer to the time field of “Completed At” (since these issues would need to be deployed). Then, I manually added a filter and chose to filter by a Status of Deployed. I was able to then see that my team deployed 54 tickets in April, 52 in May, and 25 in June so far.