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
Understanding Pulse View
Pulse view shows all the Jira issues that are part of the team's current iteration and there 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-realtime 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.
Pulse view includes the following elements:
- Jira issues - The list of issues includes the Jira issue name and the Jira issue state.
- Contributors - The list of contributors that had contributed to one of the branches that are assigned to the issue. contribution considered to be one of the following events:
- PR open
- Code changes - Code changes is the aggregated PR sizes that were recorded for all the PRs that are associated with an issue. On top of the number of code changes (counted in lines of code) it also specifies the number of repositories that the relevant branches and PRs are spread on.
- Branches - The number of active, merged, and released branches that are associated with this issue. Active branches are branches that are in the middle of the work process (either still in coding or open PR state). Merged - are PRs or branches that were merged back to the base branch and effectively their coding and review are done. Released branches are merged branches that marked as deployed.
- Issue Timeline - The issue timeline includes annotations of the GIT activity recorded for this issue. The timeline displays a daily summary of events bundled into two categories:
- Work - include: commits, PR open, and reviews.
- Completions - include merges and releases.
Hovering on each day will display the branch/PR activity breakdown for that day, including the name of the PR, activity and contributors.