Carry pull request merge context into Linear
Keep the issue current after a merge, with the closeout details available from Bitbucket.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Update issue
Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.
Why this helps
A merged change does not always make its way back to the Linear issue, leaving teammates unsure whether the work is complete.
- Record merge context with tracked work
- Reduce manual issue closeout
- Keep issue changes grounded in available data
Setup
Build it in a few focused steps.
- 1Connect Bitbucket and Linear once in the Notis portal.
- 2Create an automation in the portal, or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to review accessible merged pull request details and update the related Linear issue with a concise closeout, changing state only when the intended state is known and supported.
- 4Pick a recurring schedule as the trigger and choose where run reports should go.
- 5Test with one merged pull request and verify the related issue and any state change.
Questions about this workflow
Will this automatically find merge events?
The schedule starts the automation. Notis can review merge information available through the connected Bitbucket access; the available history depends on that access.
Can it change the Linear issue state?
The Update issue action supports state changes when supplied a valid state id. Ask for a state change only when the intended state is known and available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitbucket to Linear. A trigger fires from one place; an action lands in another.
Bitbucket triggers
Linear actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a comment
Creates a new comment on a specified linear issue.
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Bitbucket and Linear, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Linear.