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
How to - Understanding Releases
LinearB is detecting releases and following the release count in several metrics (Deployments, Deploy Frequency). Releases are counted on the repository level and counted based on the release detection strategy configured by the customer. (Learn more about release detection strategies)
A branch/PR considered released if it meets the criteria of the release detection strategy. In case you are using tags as your release strategy, all the branches in the repository that are tagged with the same tag will be a part of the release defined by this tag. In case you are using a strategy based on merging each branch that is merged will be considered as a release.
Releases are attributed to the branch contributors. If there is a contributor that committed to a branch that was released this contributor will be attributed with the release. If more than one contributor committed to the same branch, the release will be counted for each one of the contributors.
So for example, If you are using tag strategy and someone contributed to 4 different branches (in the same repository) that were tagged with the same tag, this individual will be attributed with 1 release.
If you are using one of the mergings strategies, and this individual was a contributor in 3 branches that were eventually merged into the release branch, this individual will be attributed with 3 releases.
Team level release attribution
Release (regardless of the release detection strategy) is attributed to a specific team in case it was attributed to one of the team members. However, if the same release is attributed to 2 contributors that are in the same team, only one release will be counted for the team.
If a contributor is a member of more than one team, the release will be attributed to each one of the teams this individulals this member is a part of.