Page Comparison

This section covers the Frequently Asked Questions regarding various functionalities/troubleshooting steps of PSKnowHOW.

PSknowHOW can be deployed in any cloud which can support docker. it has been already deployed in Kubernetics, AWS terraform and GCP.

PSknowHOW is fully configurable and can support any WoW as long as team is following Scrum or Kanban standards.

Go to your Jira server and select any sprint to validate as per your wish and then apply the JQL to fetch the data in Jira and compare the output with respect to KnowHOW dashboard data and start validating the data..If after doing all this you still see the data gap b/w Jira server and KnowHOW server, you can raise a DOJOSupport Request.

If sprint is deleted, you want to clean up and re fetch the items.If there are changes like date modified, name modified, restart the collector and it will get updated in DB

You have to add the IP and DNS address in the customapi.properties:

corsFilterValidOrigin=localhost,10.202.11.248

If you’re still facing any issue, then you can raise a DOJOSupport Request.

Clean up the DB and prefetch item

Project should be configured with Jira tool with Additional filters and Jira processor should be run for that project. On Kanban dashboard single project should be selected, to enable the Additional filter button.

Those defects will show up on Created vs Resolved defects KPI (if sprint is linked to the defects) and Defects Without Story Link (sprint is not mandatory) kpis.

Kanban

Yes, we can see test execution % on hovering on Sprint on KPI widget.

To log in to a specific instance, the user must use their Lion login ID and password in Active Directory. Once logged in, the user can then request access to a specific project. For more info refer Login & Access.

To troubleshoot the issues, it is recommended to verify the credentials in the connection tab. If the credentials are expired, you will need to update them in the connection tab to resolve the issue. Additionally, cleaning the data and rerunning the processor can also help in troubleshooting the problem.

Kindly refer the documentation link Install & Setup Guide.

Please refer to the link for on how to create and configure a project Configure Project & Connection

If you are seeing different POD/Track sprint names in your project sprint filter, please check your project's Jira Board query and Jira Sprint report. Additionally, ensure that the stories are correctly tagged to the appropriate POD sprint and not mistakenly assigned to another sprint.

Please verify that the user who created the Jira connection has the appropriate access permissions for the Jira Board.

Kindly refer the document Build tools Connection / Build tools Configuration.

Kindly refer the document Repo Tool Connection / Repo Tool Configuration.

Make sure that for Defect Injection Rate (DIR) KPI defects are tagged to stories, and those stories should be closed within the same sprint. Refer the doc for DIR KPI

To ensure that a story has a remaining estimate and due date, the following logic can be applied: If a story's due date is today and it has 2 days of remaining effort, the projected completion date (PCD) will be calculated by adding today's date to the remaining effort of 2 days. The PCD date will then be displayed.

Potential Delay is calculated by subtracting the Story Due Date from the PCD Date.

If a story misses its due date, it will be reflected in the Planned Completion section.

The delay for the Planned work status on the Iteration Board is calculated by subtracting the Due date from the Actual completion date.

In Initial commitment it consider Completed issue, Issues not completed, minus scope added ,Plus scope removed.