Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Release Date -

Release GitHub URL - https://github.com/PublicisSapient/PSknowHOW/releases/tag/11.0.0

DockerHub URL - https://hub.docker.com/u/psknowhow

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#E6FCFF

Key Highlights

  1. KnowHOW now guides users through a step-by-step process for setting up a new project, offering clear instructions to simplify the setup experience.

  2. Developer Board - introduced a new feature that allows users to select a specific branch and developer to track Key Performance Indicators (KPIs) trends in real-time.

  3. Recommendations on improving your delivery efficiency

  4. Enhanced Error Messaging for Jira Processor - introduced a new error handling mechanism for the Jira Processor on the Processor list page. This update will improve user experience by providing clear and specific error messages when certain HTTP status codes are encountered during the Jira integration process.

  5. Enhanced the user experience by displaying only the relevant processors configured for the selected project on the processor list page.

Note

Breaking Change

  1. To "Enable Developer KPIs" in Project Settings for existing projects with SCM tools, reconfigure the repositories using the full Git URL and run the repo tool processor.

  2. Select the most relevant repo email ID to update the developer profile in the Capacity screen. Misconfigurations will affect the developer filter available in the DEVELOPER dashboard.

Info

New Features

Expand
titleClick to see details of Features

Name

Description

Pre-Requisites

Repo Cloning

By consenting to clone your repositories, you will now be able to clone your project codebase directly to the KH Server. This approach bypasses the API rate-limiting issues that could hinder data retrieval and provides uninterrupted data access.image-20240927-121614.png

configure the repos with full Git URL

Branch and Developer filters on Developer dashboard

You could analyse data by branch or developer to track the coding activities

  1. consent for repo cloning is provided

  2. Developer names are mapped against repo email IDs in the Capacity Planning screen

Recommendations

Insights on recommended interventions in order to improve your delivery speed and quality for valuable business outcomes
Please note:- recommendations are available for a single project selection only

Collapsible header and ‘Go to Top’ icon

maximize Maximize screen space, improving user focus on the main content and quickly go to the top of the page

Improved Project Settings

Intuitive interface to set up projects and tool connections

Standardized field mappings for Quality KPIs

Error handling for no, zero or partial data

Improved Error Handling for KPI Graphs and Widgets

Focused on delivering clearer error messages and improving user guidance in cases of configuration or connection issues.

Dashboard

KPI Additions/Enhancements

RELEASE

Release Plan - Story Points & Issue Count filter is now available for Release Plan KPI

Sorting order of releases in the filters

DEVELOPER

Enhancements

Mean time to Merge - Explore Window - Merge Request Url column is added

KPI Additions

/wiki/spaces/PSKNOWHOW/pages/75726849 - The PR Success Rate helps by providing insight into the efficiency of the development process.

/wiki/spaces/PSKNOWHOW/pages/205357058 - The PR Decline Rate KPI helps by identifying areas where pull requests are not meeting the required standards.

/wiki/spaces/PSKNOWHOW/pages/197263361 - The Revert Rate KPI helps by highlighting issues with code quality and the effectiveness of the review and testing processes.

/wiki/spaces/PSKNOWHOW/pages/226459649 - The Innovation Rate KPI helps by providing insights into how much of the team's efforts are focused on delivering new features and capabilities.

/wiki/spaces/PSKNOWHOW/pages/226394113 - The Defect Rate KPI helps improve overall code quality by highlighting how often defects are addressed in pull requests.

ITERATION

  • A new field, "Issue Types to be Excluded", has been added to allow users to exclude specific issue types when configuring Estimation Hygiene and Estimated vs Actual KPIs

  • Lazy Loading of Iteration KPIs

VALUE

Value Delivery (Cost of Delay) - Value Delivered (Cost of Delay) KPI has been renamed to Value Delivery (Cost of Delay) for better clarity and Y-Axis label for this KPI has also been updated to "Cost of Delay" to improve consistency in reporting.

Dora

The Dora board is enabled for the Kanban project with two KPIs: Change Failure Rate and Deployment Frequency.

...