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
Ineffective code contribution
Looking at the commits and code that is part of a branch, we distinguish between 2 types of contribution to the branch.
Effective contribution to branch - direct commits to the branch.
Ineffective contribution - code that has a different origin branch and either merged to the current branch or cherrypicked into this branch. In this case, we are not counting this contribution as direct code changes, it is excluded from the work breakdown and commit count of the branch.
LinearB distinguishes between the 2 types of code. An Effective contribution is counted into the individual's / team's active branches (WIP) count, commit count, cycle time, and work breakdown changes. Ineffective code contribution on the other hand is already counted once on the smaller feature branch thus it is ignored when merged and is not counted for the second time.
Ineffective work on a branch is marked with a ghost icon on a branch and when hovering opens a pop-up specifying the list of direct (effective) contributors as well as the number of ineffective contributors.
Affect on individual active branches (WIP) - when someone has an effective contribution on 5 feature branches and an ineffective contribution on 2 feature branch the total number of active branches for this contributor will be 5
Affect on work breakdown and code changes - If a branch has 200 code changes that were committed directly and 500 more changes that were merged or cherrypicked from other branches, only the 500 direct changes will be counted for the work breakdown calculation.