| Panel |
|---|
| panelIconId | 1f308 |
|---|
| panelIcon | :rainbow: |
|---|
| panelIconText | 🌈 |
|---|
| bgColor | #E6FCFF |
|---|
|
This section covers the Frequently Asked Questions regarding various functionalities/troubleshooting steps of PSKnowHOW. |
KnowHOW Installation
| Expand |
|---|
| title | PSknowHOW can be deployed on any cloud? |
|---|
|
PSknowHOW can be deployed in any cloud which can support docker. it has been already deployed in Kubernetics, AWS terraform and GCP. |
| Expand |
|---|
| title | Getting 403 error page, what should I do? |
|---|
|
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 |
|---|
| title | How can I log in or gain access to the project? |
|---|
|
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 |
|---|
| title | What kind of support PSknowHOW can provide? |
|---|
|
PSknowHOW is fully configurable and can support any WoW as long as team is following Scrum or Kanban standards. |
| Expand |
|---|
| title | What are the steps to install and set up KnowHOW? |
|---|
|
Kindly refer the documentation link Install & Setup Guide. |
| Expand |
|---|
| title | Why is the Jira Board not visible when a user tries to add the Jira project key and select the Jira connection during project creation? |
|---|
|
Please verify that the user who created the Jira connection has the appropriate access permissions for the Jira Board. |
| Expand |
|---|
| title | What are the steps to set up build tools such as Jenkins, Bamboo, Azure Pipeline, etc.? |
|---|
|
Kindly refer the document Build tools Connection / Build tools Configuration. |
| Expand |
|---|
| title | What are the steps to set up Repo tools such as GitHub, GitLab, Bitbucket, Azure Repo, etc.? |
|---|
|
Kindly refer the document Repo Tool Connection / Repo Tool Configuration. |
| Expand |
|---|
| title | Why can't I see the assignee in Capacity Screen/Iteration/Daily Standup? |
|---|
|
Make sure to enable the Individual KPI Toggle while creating a project to view the assignee details. |
Project Configurations
| Expand |
|---|
| title | How to setup a project and configure a connection in KnowHOW? |
|---|
|
Please refer to the link for on how to create and configure a project Configure Project & Connection |
Run Processors
| Expand |
|---|
| title | What should I do if I encounter a processor failure? |
|---|
|
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. If you are using DOJO Jira, make sure to select Bearer Token authentication and add your Personal Access Token (PAT) in the connection tab. Don't forget to validate the connection.
|
Generic KPI Question
| Expand |
|---|
| title | How to validate PSknowHOW KPI's dashboard data? |
|---|
|
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, namemodified, restart the collector and it will get updated in DB
| Expand |
|---|
| title | Getting 403 error page, what should I do? |
|---|
|
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. |
| Expand |
|---|
| title | What If I delete some stories in JIRA. Does it is still visible in PSknowHOW KPIs Dashboard? |
|---|
|
Clean up the DB and prefetch item |
...
| What is the next option if client is not following Agile? |
|---|
|
Kanban |
Speed KPI
Quality KPI
| Expand |
|---|
| title | What are the likely scenarios when "no parent" stories are linked to defects in client environment? |
|---|
|
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
...
| Any option to see the sprint name in test execution % kpi widget where we can see the test execution data? |
|
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.
| Expand |
|---|
| title | What should I do if I encounter a processor failure? |
|---|
|
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. |
| Expand |
|---|
| title | What are the steps to install and set up KnowHOW? |
|---|
|
Kindly refer the documentation link Install & Setup Guide. |
...
| title | How to setup a project and configure a connection in KnowHOW? |
|---|
...
| Why is there a mismatch in the data for defect injection KPIs? |
|
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 |
| Expand |
|---|
| title | How is DIR and Defect Density calculated in KnowHOW? |
|---|
|
Defect Injection Rate/Defect Density | NUMERATOR: If a defect is tagged to the story that is tagged to the sprint, it is considered If a story spills, then defect will be considered in the sprint when story gets closed Defects that were raised earlier/defects raised but not tagged to sprint will be considered
DENOMINATOR: All stories closed in the sprint (irrespective whether they had any defect) EXCLUSION: Defect is raised tagged to the sprint but the corresponding story not tagged to sprint |
|
Value KPI
Iteration Board
| Expand |
|---|
| title | What happen in Jira when we delete OR make some changes in Sprint. Does it still show deleted/changes made in the Sprint in PSknowHOW ? |
|---|
|
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 |
|---|
| title | Why is my project sprint filter showing different POD/Track sprint names in the filter? |
|---|
|
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. |
...
| title | What are the steps to set up build tools such as Jenkins, Bamboo, Azure Pipeline, etc.? |
|---|
...
...
Please verify that the user who created the Jira connection has the appropriate access permissions for the Jira Board.
| How prediction completion date (PCD) is calculated on the Iteration Board? |
|
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. |
| Expand |
|---|
| title | How Potential Delay is calculated on the Iteration Board? |
|---|
|
Potential Delay is calculated by subtracting the Story Due Date from the PCD Date. |
| Expand |
|---|
| title | How is the Planned Completion calculated for the Planned Work status on the Iteration Board? |
|---|
|
If a story misses its due date, it will be reflected in the Planned Completion section. |
| Expand |
|---|
| title | Explain the process of calculating delay for the Planned work status on the Iteration Board? |
|---|
|
The delay for the Planned work status on the Iteration Board is calculated by subtracting the Due date from the Actual completion date. |
| Expand |
|---|
| title | In the calculation of commitment reliability KPI, are issues that are completed, not completed, removed, or added during the sprint considered? |
|---|
|
In Initial commitment it consider Completed issue, Issues not completed, minus scope added ,Plus scope removed. |
| Expand |
|---|
| title | How is DIR and Defect Density calculated in Iteration Board "Quality Status KPI" |
|---|
|
| Iteration Dashboard | Defect Injection Rate/Defect Density | NUMERATOR: If a defect is tagged to the story that is tagged to the sprint & defect itself also tagged to sprint, it is considered DENOMINATOR: Linked stories to the defects that are counted are considered (Closed story with or without defect, In progress story with defect) EXCLUSIONS: If the defect is raised during sprint 'n' and tagged to sprint n+1 inspite of the story being tagged to sprint n, it will not be considered in any sprint |
|
| Expand |
|---|
| title | Why am I not getting the correct data on the Wastage KPI? |
|---|
|
There are two configuration options: Blocked issue and Include flagged issue. Make sure to select one of these options. Update the mapping for "Status to Signify queue" (e.g. Ready for Testing, Code Review).
|
| Expand |
|---|
| title | The end date of the sprint does not match with the Jira sprint end date. |
|---|
|
|
...
Kindly refer the document Repo Tool Connection / Repo Tool Configuration.
...
| steps should I take if an active sprint is not visible in Iteration Board of KnowHOW? |
|
If you encounter an active sprint that is not visible in KnowhOW, consider any recent changes in Jira teams or board configurations, as well as any alterations in team assignments. Ensure that updates regarding board names, teams, or any other relevant changes are reflected accurately in KnowhOW configuration
|
Release Board
DORA
Developer KPI
Backlog KPI
KPI Maturity
Kanban Board KPI
| Expand |
|---|
| title | How can I see customize filters on Kanban board. |
|---|
|
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. |