Make aging pull request follow-up easier to spot
Bring a concise reminder to the Linear issue when an accessible pull request appears to need attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create a comment
Creates a new comment on a specified linear issue.
Why this helps
Pull request follow-up can slip when activity is spread across tools and no one has a simple reminder in the issue tracker.
- Make follow-up visible on the related issue
- Reduce manual checks for waiting work
- Keep reminders grounded in available activity context
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 pull requests for provided age or inactivity details and comment on the related Linear issue only when the configured follow-up condition is met.
- 4Pick a recurring schedule as the trigger and choose where run reports should go.
- 5Test with one real pull request and confirm the reminder is appropriate and linked to the right issue.
Questions about this workflow
Can Notis calculate how long a pull request has been inactive?
Only if the connected Bitbucket data exposes the relevant dates or history. If it does not, provide the age or inactivity detail in the available context.
How do I control when a reminder is posted?
State the condition in your instruction, such as a minimum period without activity. Make sure the needed activity data is available to Notis.
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.