These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
John Musa suggested an idea (#5075) · Apr 17, 2020 at 03:04 PM · usability
Per ATF User Community [ATF-5185] -- Since Reservation ID, Job Number and Job Name are available information to Cloudshell, currently, they are not displayed at the heading info group. The user needs to open the log and retrieved the reservation ID. To make it user friendly, add the available information for user easy reading. So, the user can make a screenshot, capture all the necessary information. No need to go more steps to collect information.
More details are necessary for this idea/requirement.
Terry Vaughn commented · Jun 02, 2020 at 06:09 PM
Hi, John - Can you provide some more info?
Extend your CloudShell capabilities by creating your own Shells. Share your knowledge with the world and be part of our growing community
Help us make things better. Share your great idea or vote for other people's.
Filter ports not relevant to the route type
Identify resource associated with posts to output window
2nd gen shells: ability to add different icons per resources of the same shell
Script parameters enhancements
Replace the resource hover menu with a regular context menu
Double click to open remote connection
Change owner of test suite -- by domain administrator or system administrator.
Allow option to shorten port names when a resource is autoloaded
Enable/Disable Guacamole links on a Resource Level
Allow non-controlled attributes to be part of Shell Standard