Release Date: Sep 17, 2020
Projects Pulse View - Face Filter
Pulse view shows all the Jira issues that are part of the team's current iteration and their 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 real-time 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.
Face filter allows the user to filter and focus on a single team member. Clicking on one of the team members will leave only the issues that this team member had a contribution in, filter out all the other issues. Furthermore, when focusing on a single member, all the other work done by other team members in this issue will be greyed out so it is easier to focus only on the work done by the relevant team member.
With face filter, the user can check whether team members had hi-level of context switching during the iteration, hi-level of utilization, see if work is balanced between the different members of the team, and whether or not there are issues that are stuck or delayed.
Pulse view - Change issue state
LinearB now allows users to update the state of the issue (both in LinearB and in Jira) directly from the Pulse page. If for example, the user sees, based on Pulse that all the branches and PRs associated with this are done. In such a case, when the issue in Jira showing the wrong state, the user can choose to change the state of the ticket from “In progress” to “Done” directly from Pulse. By doing this, the state of the issue will be updated in LinearB and in Jira. LinearB will also update the Jira ticket and leave a comment regarding the state change
LinearB made the onboarding process easier, faster, and more friendly. We reduced the onboarding steps and removed the need to select the Git provider. In addition, LinearB guides the user to connect to Jira and connect teams to the Jira board in order to get the max out of LinearB. Once the initial onboarding data processing is over LinearB points the user to 3 main use cases for immediate value.
Metrics (Performance) improvements
We changed the reports to be more suitable for dev teams’ needs. There are now 3 reports for:
Delivery - includes all the cycle time metrics - with a breakdown of each cycle time metric separately.
Quality - The quality report includes metrics that indicate the quality of the work including average PR size, Review depth, and work breakdown.
Throughput - The throughput report includes metrics based on quantitative performance like code changes, PRs merged, and releases.
In addition, we added the option to look at each metric not only based on fixed time frames (daily, weekly, monthly) but also based on iterations thus getting the change in as metric from one iteration to the next.