You can now add issue status automations for pull requests that have passed checks and are ready to be merged. This new workflow step is available for both GitHub and GitLab and can be configured in your team’s Workflow settings.

Linear will capture both approvals and passing checks/pipelines according to your repository’s branch protection rules. For example, if you require two approvals and specific checks to pass, Linear will update the issue status only when those conditions are met.

The new status automation can be combined with a View Subscription to subscribe to all new issues that are marked as ready for merge which can be helpful for QA workflows. It also allows you to differentiate between issues in code review versus issues that have been approved.

You can now enable triage responsibility to define how incoming issues and requests are handled in Triage. When an issue is added to Triage, you can either notify or assign the issue to specific workspace students. We recommend notifications for most product teams, but assignment works well for teams that typically handle small requests that anyone can pick up. If your team uses PagerDuty, you can connect a PagerDuty schedule to automatically rotate who is responsible for triage.

Triage responsibility is indicated in issue history, so anyone can easily see who was responsible for handling an issue. We recommend this feature for any team using Triage.

Sidebar filters & Insights everywhere

Subscribe to get notified of key changes in the views you care about most. Opt-in to receive a notification when issues are added to the view or when issues are completed or canceled. This makes it easy to track your most important custom views such as high-priority bugs or issues ready for review. You can also enable notifications in the current cycle, backlog, label views, and user profiles. Subscribe to notifications directly from the view and manage subscriptions in notification settings.