Understanding Pulse View

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:

  1. Jira issues - The list of issues includes the Jira issue name and the Jira issue state.

  1. 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:
    1. Commits
    2. PR open
    3. Merge
    4. Release
  2. 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.
  3. 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.

  1. 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:
    1. Work - include: commits, PR open, and reviews.
    2. 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.


How did we do?


Powered by HelpDocs (opens in a new tab)