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 - Use Slack commands
Slack commands help individual developers to easily access information about their work or work that is assigned to them. With Slack commands, developers can save time and effort every morning and during the day and see the latest status, and the latest activity on each PR they are working on and each review that is assigned to them.
The following commands are available
Show the list and short explanation of all the available slack commands
This command provides the developer a summarized list of all the latest PRs that were recently updated. This list will include PRs that I am the owner of as well as PRs that are waiting for my review and PRs that I'm reviewing. Each PR will show the state of the PR, the last activity on the PR, and the owner (where relevant).
This command provides the developer a summarized list of all the latest PRs that are waiting for my review and PRs that I'm reviewing. Each PR will show the state of the PR, the last activity on the PR, and the owner of the PR.
This command provides the developer a summarized list of all the latest PRs that s/he is opened and are still in active state. the last activity on the PR, and the state of the PR.
/lb prs long
This command provides the developer a summarized list of all the PRs that s/he is opened and are active for a very long time.
/lb prs done
This command provides the developer a summarized list of all the latest PRs that s/he is opened and were recently either merged or merged and released
This command allows the developer to control her personal notification and provides an interface to opt-in/opt-out from each one of the available notifications.
This command allows the developer to unlink her slack handle from LinearB and in fact disconnect her slack account from LinearB disconnecting from both LinearB Slack commands as well as LinearB personal notifications.