Hi Jagadeesh,
thanks for your reply.
This not a solution, but a useful workaround I've already set and explained to the end-user.
Unfortunately the execution statuses shouldn't be a simple list of options should be a configurable set of options by the Jira administrator to restrict the editing permission depending on the current status. This is the only way to avoid the end-user make a mistake in selecting a not-compliant status or forget to choose 'Done' in the workflow.
The automatism is essential: any final status of the execution should be irreversible. The final status are PASS (built-in status) and 'N/A' (custom status).
If the user forget to select 'Done', the execution status could be edited by anyone!
Even if the execution history can help identifying who change the execution status and when, the process is not compliant to the standard ISTQB and the KPI gadget becomes incongruous.
For example, an end-user reopen a test execution and change the status from 'N/A', not applicable, to WIP, work in progress; the action is not compliant to the test management standard (N/A is a final status) and the filter that collect all opened statuses includes this execution so the gadget 'Test Execution Details' displays this execution as if the testing team is working on it while it should be count as finished, no more work needed (performance degradation is not real!).
The Zephyr execution workflow is focused on the time tracking not on the process, unfortunately!
This tool is missing some needed features. Hope the next releases can be better than this!
Best Regards,
GP
