Hi everyone,
we noticed recently, that there are a few cases in our Jama, when Test Runs are being unintentionally user locked.
One use case we found, how it probably happens is when one closes the main Jama window during the test run execution and continues executing the test run. After saving such test run it stays user locked.
Is this seen as an intended behavior or is there a bug logged for it?
Is there another known issues when the Test Run gets unintended user locked?
Thanks and best regards,
------------------------------
Ekaterina
------------------------------