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
Release Date: Nov 5, 2020
Projects Pulse View - Delivery Alerts
Pulse view shows all the Jira issues that are part of the team's current iteration and their actual GIT-based progress and work.
LinearB matches the relevant branches and PRs to the relevant Jira issues and provides the user with relevant and near real-time data on each issue based on the actual work as it is recorded in the user's GIT data. This view provides the user with a much more accurate and comprehensive understanding of the actual work that is done for the issue and disconnects the reliance on the Jira hygiene of devs.
Delivery alerts focus users on issues that are currently stuck and may delay the release of value to customers. Delayed issues are marked with an orange alert icon to the right of the issue and provide context on the reasons issues are stuck
- PR awaits review
- PR Review is too long
Once the PR is merged and this delivery bottleneck is released, the alerts are dismissed.
Slack Notifications - provide issue context
LinearB now adds to delivery notifications (PR awaits review and PR with long review) the context of the relevant issue related to this PR. This provides the user with context regarding the relevant issue that this PR is delaying.
Slack Daily Digest - Stuck work
LinearB now adds to the daily digest Slack notification information about issues that are currently (for the relevant day) are stuck and either await someone to start to review. Or, its review takes too much time.
In addition, each PR is linked to the PR page in git.
LinearB now provides the user with indications about team members that are stressing their work to a point they might reach burnout. The indication is based on consecutive active days.