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
Cycle time is one of the most interesting engineering execution metrics. It will show the average time it takes for a single engineering task (usually mapped to a branch) to go through the different phases of the delivery process from 'code' to 'production'. Cycle Time refers to the following subsets:
The time it takes from the first commit until a pull request is issued. In this widget, it's represented as the time frame between 'First Commit' to 'PR Issued'.
The time it takes from when a pull request is issued until a review has started. This part indicates how strong teamwork is and it usually has a big impact on the cycle time as very often is where Pull Requests get stuck. In this widget, it's represented as the time frame between 'PR Issued' to 'PR Reviewed'.
The time it takes to complete a code review and get a Pull Request merged. In this widget, it's represented as the time frame between 'PR Reviewed' to 'PR Merged'.
The time it takes to release code to production. LinearB tracks each release tag and knows to map it back to branches and present how much time completed tasks 'waited' to be deployed. In this widget, it's represented as the time frame between 'PR Merged' to 'Release'.
Note: Cycle time refers to all the branches that were being updated during an iteration or a workweek.
For example, if a branch went through the first phase here (Pull Request issued) it will already be taken into account. In oppose to the 'time to merge' delivery metric that will only be calculated for a pull-request that went throughout all the phases until the merge. This is why at times there can be discrepancies between the two.
To learn more about how LinearB uses industry benchmarks