Frequently Asked Questions

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

PSknowHOW can it 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.

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.

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.

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 Das

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

I am getting 403 in UI

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

corsFilterValidOrigin=localhost,10.202.11.248

I have deleted some stories from JIRA,but it is still visible in KPIs

Clean up the DB and prefetch items

Need, customize filters for Kanban board.

And there are no parent stories for the bugs in client environment

Due to some client workflow process, they are not much agile so how to use KnowHOW for this kind of scenarios. As Client is using managed service

There should be an option to see the sprint name in test execution % kpi widget so that it will be easy to see the test execution data.

The default benchmark dotted red line for defect injection rate should be configurable otherwise it is questionable for most of the clients.

The defect removal KPI average calculation is happening wrongly e.g. there are 4 sprints and 2 sprint has 20,30 defect removal but in remaining two it is 0 so when it shows in aggregated view it is averaging from all four sprints.