KnowHOW Release v7.10.0.

Release Date - 5-Oct-2023

Key Features Released

Enhancements

• Defect by Testing Phase KPI

  • The Release dashboard provides access to the KPI.

  • This KPI is particularly beneficial for teams that undergo multiple testing phases during a release.

  • It enables teams to monitor all defects identified during a release, with the added feature of categorizing them based on the testing phase in which they were discovered.

  • Teams have the flexibility to use labels, components, or any custom field to identify defects that arise during a testing phase. This can be configured under Settings -> Jira Mappings.

• Lead time for Change KPI

  • The DORA KPI is derived from information available in backlog tools such as Jira or Azure.

  • This KPI records the duration from the time of commit to production.

  • The graph displays the average lead time for all issues that were productionized within a week.

  • The central vertical column presents the overall average lead time.

  • Additional details such as Lead Time in days, Completion Date, Merge Date, Release Date, Merge Request ID, and Branch can be accessed by clicking on the overlay.

  • The Lead Time calculation can be performed in two ways: through Jira or through the Repository (Repo).

    • If Jira is selected in the configuration, the KPI calculates lead time by determining the interval between the Completion Date and the Release Date, and then displays this lead time.

    • If Repo is selected in the configuration, the KPI calculates lead time by determining the interval between the Merge Date and the Release Date, and then displays this lead time.

• Iteration Readiness KPI

  • Iteration Readiness KPI provides insights of how well the stories (issues) are refined in the upcoming 5 iterations.

  • This helps users identify the state of refinement for upcoming iterations and ensure attention is given to refinement if the state is bad.

  • This can be configured under Settings -> Issue type Mappings for e.g.(Story, Defect, Change request).

• Developer Board

  • A new dashboard has been created which is called as the ‘Developer’ dashboard. All Repo KPI’s have been moved here. The current set included

    • Mean time to merge KPI.

    • Number of check-in and merge requests.

  • This dashboard will get many more KPIs in the next few months.

• Tabular View

  • A new feature has been added that enables users to view the KPIs of five sprints simultaneously in a single, scroll-free view.

    • This feature is only applicable when a single 'project' is selected. It will be disabled if multiple projects are chosen.

    • The feature will also be disabled if any higher hierarchy is selected.

  • By hovering over the values in the Frequency column, users can gain insights into the details of Sprints 1 to 5, Weeks 1 to 5, etc.

• Release Progress KPI

  • The Release Progress KPI has been improved by substituting the Priority and Assignee filters with an Issue Type Filter.

  • Users now have the ability to click on the horizontal bars of the graph to view detailed status information. For instance, clicking on the "In Progress" bar will display the count of issues with the "In Progress" status, such as In Analysis, In Development, etc. The same behavior applies when selecting Story points.

Note : Upgrade Steps:

Kindly run the provided upgrade script by connecting to your preferred client after mongo instance is up
Upgrade Script