LinearB Slack Application Updates
Frequently Asked Questions
Connect to Jira and set the board for your team
Set up your initial team
LinearB Trial Setup
Github server (on-prem) connection guide
BitBucket server (on-prem) connection guide
GitLab server (on-prem) connection guide
Connect Github with a personal access token
Set up release detection method
Jira (cloud) connection guide
Jira server (on-prem) connection guide
How to create a Clubhouse API token
Troubleshoot - Can't find my repositories after authorizing LinearB in Github
Connect LinearB to your Project Management Tool
How to - Create and manage teams
How do I connect and manage WorkerB Team Alerts?
How to - Invite new users
How to - Work with team dashboard
How to - Handle High Risk Work
How to - Handle Material Pull Request Merged w/o Review or Basic Review
How to - Handle Hanging Review Requests and Long Reviews
How to - Manage and Customize Notifications
How to - Re-authorize git integration
How to - Merge accounts
How to - Use Slack commands
How to - Understanding Releases
How to - Set Jira board per team
How do I set up WorkerB Personal Alerts and Commands?
How to - Re-authorize GitLab integration
What is Cycle Time for Software Developers?
Detecting high risk work
Lightning PRs action filter
Long Living PR Action Filter
Using the App
What is "Work Breakdown"?
Code Change Rate
PR Open Rate
Time to Merge
Issues Done / Story Points Done
Pull Request Size
WIP (Work In Progress)
Done in Iteration
Point in History
Carryover from Iteration
Pull Request Filters
Updated in Iteration
Lightning Pull Requests
Review Request Hanging
Long Living Pull Requests
Pull Request State
Merged Without Review
Merged in Iteration
High Interaction Pull Requests
Understanding Pulse View
Draft Pull Requests
Pulse naming conventions - Jira
Pulse naming conventions - Clubhouse
Ineffective code contribution
Projects active contributors
Metrics Community Benchmarks
Work Breakdown Terms
Understanding Code Changes
Quality Code Metrics Explained
Updated by Boaz Dremer
This document will walk you through how to utilize LinearB in your daily workflow.
1) Identify Unreviewed Pull Requests:
Identify pull requests that have been merged without review. Pull requests that are merged without review increase quality risk, decrease efficiency, and slow new value delivery.
Navigation: Activity → Pull Requests → Predefined Filters: “Merged Without Review”
2) Proactively Address Risky Work in Branches
Detecting risky work in branches allows for proactive quality risk management. Identify risky branches early and ensure proper inspection and review.
Navigation: Dashboard → WIP → Predefined Filters: “High Risk or High Rework”
3) Contributor Workload (WIP)
Identify contributors that are overloaded with WIP. Having contributors overloaded with work will decrease your cycle time, increase risk for late iteration delivery, and increase risk for contributor burn out.
Navigation: Contributors → Sort by “WIP”
4) Long Living Pull Requests (Stuck PRs)
Identify pull requests that have been open for too long. Pull requests that have been open for too long degrade in quality, decrease cycle time, and increase risk. Find them and push them forward.
Navigation: Activity → Pull Requests → Predefined Filters: “Long Living”
5) WIP vs. Completed Work
See how much work your team has in progress and how much work your team has completed. Compare your WIP to your remaining iteration time to improve iteration predictability.
Navigation: Dashboard → WIP / Done