ContributionsMost RecentMost LikesSolutionsPurpose of support tools for technical discussions, bugs, feature requests and more Coming from the link to the new portal for Zephyr Scale ideas that Rache1 gave herehttps://community.smartbear.com/t5/Zephyr-Scale-Questions/Test-cycle-freeze-when-done-in-Zephyr-Scale/m-p/247480/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExGTEdHUkxLWjhVMzhUfDI0NzQ4MHxTVUJTQ1JJUFRJT05TfGhL#M2443,I want to ask about the purpose of those tools because the multitude of platforms for talking to SmartBear support and placing/finding information is confusing me. There is https://smartbear.atlassian.net/servicedesk which holds support requests. There I can only see my own tickets. I got comments from supporters with JQA-1234 tickets that I cannot see anywhere, so I cannot read what a supporter has written in that ticket, whether it has ever been started to work on or what its status is. Do these tickets still exist? How can I access them? There was the possibility to send e-mails to support without logging in to the portal which I often made use of. That mail address jira@smartbear.atlassian.net does not seem to always be read or processed. Some requests to there have been unanswered for quite some time. In former times I received replies with ticket keys that were created. Yet, I do not remember (or can find) any information of that address being abandoned by SmartBear. What is the status of it? The aha! portal seems to be no longer available. What happened to the links in there and their information? Then there is the new https://community.smartbear.com/t5/Zephyr-Scale-Questions/bd-p/ZephyrScale . Its purpose seems to be to discuss questions and issues but once they turn into or refer to a ticket, this (external) information is no longer visible for participants, so it lacks transparency. What is the strategy of separating all this information into different tools and creating barriers between them? With (at least some of) those platforms no longer being in use, the links not working any longer and no substitute being in place, it seems that a lot of information is not accessible any longer. Information about created tickets, bug reports, feature requests, their ticket or planning status. What happened to the tickets that have been created in various tools over the years? Is there a strategy for keeping this information together in the future, migrating them to one tool, visible for the customer, linked to each other so that it stays transparent in the long run and that the customers do not have to file the same issues again and again? My summary and thus the basis for my confusion: customer bug reports, customer change requests, employee tickets - everything that should be under one hood is split across different tools with a lot of media breaks, isolated accounts and information. And as a funny side note: none of them is Jira, THE tool for incident tracking for which SmartBear develops and sells us add-ons 😕 Re: Unable to spy the objects desktop application I'm not using TestComplete, please don't tag me for that. Re: JIRAUSER12345 instead of user name in Excel report The question basically is: if it can display the clear name of a user on the webpage, why can it not write it to a file? Obviously the module has the information about the clear name. The export functionality is a functionality of Zephyr Scale, so it should be in SmartBear's hands. At least a pragmatic way around it would be to have two export options: 1) clear names and 2) obfuscated. Re: Test cycle freeze when done in Zephyr Scale Thanks for your reply. The separation into different tools was unnecessary and became a big disadvantage for customers. It made it very intransparent to see which bugs and feature requests are already existing and discussed by other customers and the vendor. This all belongs into one platform visible for every paying customer. Even more as they are selling software for exactly that purpose - incident tracking and test management. Re: Feature request: URL custom field type Basic, and would be very useful. Re: Test cycle freeze when done in Zephyr Scale Can you please give the link to your feature request? This feature is long overdue. I filed it years ago in the old ticket system but it had only been closed. It seems it was never worked on. JIRAUSER12345 instead of user name in Excel report I found a similar question here https://community.smartbear.com/t5/Zephyr-Scale-Questions/Unable-to-add-owner-field-when-imported-test-case-via-csv-file/m-p/240078/highlight/true#M1904but want it to be answered more generic. When we use Zephyr Scale's reports in Jira, e.g. "Test execution results (list)", it shows the user names as clear text in the browser window for all users. When the same report gets exported to Excel, for some users it shows JIRAUSER12345 instead of the user alias in fields “Execution.Assigned To” and “Execution.Executed By”. According to https://community.atlassian.com/t5/Jira-questions/User-showing-as-an-ID-value-instead-of-users-name/qaq-p/1684514, it seems to be a GDPR -compliance measure. I am not convinced by this argumentation because it is an incomplete approach that does not solve anything, it only generates additional work for the user: either to restore the obfuscated IDs back to the real user names, or to anonymize all other user names manually. In both cases the current implementation is a failure. How can I get the Excel report to write out the user names as can be seen in the web report?