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 - Merge Accounts
LinearB is allowing now to merge similar git accounts with different aliases or emails that appear today in LinearB as 2 separated accounts. The problem this issue causes today for users is that even though it’s 2 git accounts in fact it is a single person. Users want to see work and metrics for the person (as one) and not two or more sets of metrics as it appears today.
By letting users control accounts and merge them into a single alias LinearB provides users the option to see all wark and metrics aggregated and summarized under a single account.
Merge accounts management is available through the “People” navigation. Hovering over a single account row will show users a menu option.
Selecting the option to merge a specific account will open a dialog that will provide a list of all available contributors (found in the Git accounts) and the user will be able to select one or more accounts to merge with the original account selected. LinearB will offer the most relevant accounts as merge candidates.
Selecting accounts to be merged will add the selected account to the merge list. The primary user is the user that all other accounts will be merged into, meaning they are getting the alias and teams association of the primary account.
Once accounts are merged all metrics and data of all merged accounts will be calculated into the single merged account.
Merged users are marked with a “merged” icon next to the account’s details. Users can edit and un-merge accounts and revert back to the ‘original’ accounts.