| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This section covers the Frequently Asked Questions regarding various functionalities/troubleshooting steps of PSKnowHOW. |
KnowHOW Installation
| Expand | ||
|---|---|---|
| ||
PSknowHOW can be deployed in any cloud which can support docker. it has been already deployed in Kubernetics, AWS terraform and GCP. |
| Expand | ||
|---|---|---|
| ||
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. |
KnowHOW Project Access
| Expand | ||
|---|---|---|
| ||
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. |
KnowHOW Project Setup
| Expand | ||
|---|---|---|
| ||
PSknowHOW is fully configurable and can support any WoW as long as team is following Scrum or Kanban standards. |
| Expand | ||
|---|---|---|
| ||
Kindly refer the documentation link Install & Setup Guide. |
| Expand | ||
|---|---|---|
| ||
Please verify that the user who created the Jira connection has the appropriate access permissions for the Jira Board. |
| Expand | ||
|---|---|---|
| ||
Kindly refer the document Build tools Connection / Build tools Configuration. |
| Expand | ||
|---|---|---|
| ||
Kindly refer the document Repo Tool Connection / Repo Tool Configuration. |
Project Configurations
| Expand | ||
|---|---|---|
| ||
Please refer to the link for on how to create and configure a project Configure Project & Connection |
Run Processors
| Expand | ||
|---|---|---|
| ||
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. |
Generic KPI Question
| Expand | ||
|---|---|---|
| ||
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. |
...
| Expand | ||
|---|---|---|
| ||
Kanban |
Speed KPI
Quality KPI
| Expand | ||
|---|---|---|
| ||
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. |
...
| Expand | ||
|---|---|---|
| ||
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 |
Value KPI
Iteration Board
| Expand | ||
|---|---|---|
| ||
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 |
...
| Expand | ||
|---|---|---|
| ||
In Initial commitment it consider Completed issue, Issues not completed, minus scope added ,Plus scope removed. |
Release Board
DORA
Developer KPI
Backlog KPI
KPI Maturity
Kanban Board KPI
| Expand | ||
|---|---|---|
| ||
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. |
...