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 - Set up Jira board per team
In order for a team get its own iterations and its own Jira issues (for Pulse view) It is imperative to select the relevant Jira board and relevant iterations for the team.
LinearB provides each team the option to set up the team's board and furthermore filter the relevant iterations using a regular expression or manually select the iterations.
Team board selection is done through the team setting area on the "Jira" sub-navigation. If the organization is connected to Jira the user will be given the option to select the relevant board for the team.
Once the board is selelcted the user will be able to see the number of the iterations in the board and the names of the iterations. If necessary the user will be able to:
Add a regular expression that will filter the relevant iterations from the board according to a specific naming convention. Once the user adds a regular expression the list of available iterations is updated.
The last level of filtering is available through manual filtering of specific iteration names. Through this option, the user can uncheck any specific iteration that might be irrelevant for her team.
Once the list of iteration is set LinearB will process the new board settings and change the available sprints and issue data based on the new selection.
Note: It will take few minutes to re-process the team's data after board/iterations changes. Only after LinearB processed the data for the new board/iteration it will be displayed in the dashboard.