Forum Discussion
HI Jener ,
This is issue for only few customers.
There was a new version of Zephyr that was released (8.0.1) over the weekend (10/9-10/10) which is what has caused this issue. We have already identified a root cause and will be deploying a fix so that it does not impact any more customers.
Root Cause
We had earlier (couple of weeks back) fixed an issue with some language settings that would check and automatically create TEST issue type for different languages. During 8.0.1 release since there were Atlassian descriptor changes this effectively re-installed the application which triggered the language change to kick in and it has incorrectly modified the registered TEST issue type. This has not resulted in any data loss and all the data is still available.
Next Steps
If you/your instance has been impacted, please reach out to our support so that we can manually reset your TEST ID which should bring your tests back and should restore full functionality.
Thanks
Jagadeesh
Hi,
thanks, where do I find the test id? we have a planned release to production tomorrow and a go no go meeting based on the Zephyr results today.
BR,
Jenny
- Jener3 years agoOccasional Contributor
Hi,
now it suddenly works again, I found out while looking for the "test ID" 🙂
Thanks and hope it stays stable now.
BR,
Jenny
- Jener3 years agoOccasional Contributor
JagadeshMadhura I still have a user who cant see any tests in the testcycles. Is the TEST ID personal? please help.
BR
Jenny
Related Content
- 3 years ago
- 5 years ago
- 12 months ago
- 4 years ago
Recent Discussions
- 12 days ago