Understanding the Pulse View

Understanding the Pulse View

Pulse view takes all PM (Jira or Shortcut) issues that are part of a team's current iteration and combines these issues with the actual Git activity occurring on branches linked to these issues. This view provides you with a much more comprehensive understanding of the work that is being accomplished on an issue and can reduce the amount of effort required by developers to update their PM issues.

Pulse reports are specific to each team created in LinearB. Teams can then be linked to Jira or Shortcut PM boards in order to activate Pulse. Read more about creating teams and linking teams to boards below.

How do I create, edit, and delete teams?

How do I connect project management boards to a team?

In order for LinearB to correctly map git activity to PM issues, please follow standard PR naming conventions, specifically including the Jira or Shortcut issue ID in your Git branches and/or PRs

Filtering your Pulse report:

In order to access Pulse, click on the Pulse tab, and select the team whose activity you would like to review. You can filter the issues displayed by issue type, issue status, and also search within issues for issue ID or title.

Data included in Pulse issues:

  1. PM issue - The issue name, story points, and state. You can change the status of issues directly from LinearB using the dropdown menu.
  1. Contributors - The list of developers who have made contributions to the branches assigned to the issue. To be a contributor, a developer must do one of the following actions: commit, open PR, merge, release.
  2. PR Size / Code Changes - This number is the combined number of code changes (counted in lines of code) that were recorded for all the PRs that are associated with an issue. You also see the number of repositories that the branches linked to this issue are touching.
  3. Branches - The number of active, merged, and released branches that are associated with this issue. Active branches are branches that are either still in coding or open PR state. Merged branches are PRs or branches that have been merged back to the base branch. Released branches are merged branches that are marked as deployed.
  4. Issue Timeline - The timeline of Git activity on branches linked to this issue. The timeline displays a daily summary of events bundled into two categories:
    1. Work (purple)- commits, PRs opened, and reviews
    2. Completions (green) - merges and releases
A note on subtasks: Git activity associated with a subtask in the PM tool will be bundled with the parent story and displayed in the Pulse view, but the subtask will not be broken out on its own.

Hovering on each day will display the branch/PR activity breakdown for that day, including the name of the PR, activity, and contributor.

Unlinked Branches

Git branches which have been created by your team but not connected to PM issues are listed at the bottom of your Pulse page. You can click directly into these branches to update the branch with a PM issue ID in order to link the branch to an issue ticket. Branches can be linked to PM issues by including the issue ID in the name of the branch, or in the name of the PR linked to the branch.

Pulse Retroactive View

Clicking on the iteration filter at the top of your Pulse page will allow you to select previous iterations and receive a detailed report of your activity in that week or sprint.

Planning Accuracy: How much of your planned tasks were completed?

Planning accuracy measures the ratio between planned issues or story points and what were in fact delivered from that list. Accuracy < 70% indicates potential over-commit. Accuracy > 95% indicates potential under-commit. This percentage is calculated using the number of completed (not including added) issues/story points divided by the number of planned issue/story points.

Delivery: How well did we complete our planned tasks?

The delivery section breaks down

  • Completed - Planned story points or issues completed in a sprint.
  • Unplanned - Story points or issues added and completed after the sprint begins. Note that this does not take into account unplanned issues which were not completed.
  • Uncompleted - Planned but not completed story points or issues.
  • Planned - Story points or issues added before or within 24 hours of a sprint beginning.
Investment Profile: What type of work did we complete?

The investment profile page uses data from your project management platform to visualize the investment being made by issue type. LinearB will display all issue types found within the boards connected to your team.

People Effort

This percentage of team members who have completed issues in this iteration or week. A team member will be counted in this metric if they are assigned to an issue when it is moved to "done" status. This number of "active" contributors will be divided by the number of developers in your team.

Delivery Breakdown: What issues did we work on?

Listed on the right of your page are all issues collected for your team in this past iteration. Issues are divided by their status as listed in the Delivery row. Click the "View more" link next to any segment in order to see all issues. Clicking on any issue will take you to your Jira or Shortcut platform to see the full issue.

How did we do?

Powered by HelpDocs (opens in a new tab)