Feature Requests & Ideas

The Workspace report is something I get daily and it's a great way to assess the health of my different applications. However currently it's not ordered clearly and I'd want to see all plans grouped by application.Applications with failing pla...

On the dashboard, I have a great overview through the Environment Status. However it's showing me the status of disabled plans. Here (Image attached) showing me the status of disabled link crawl plans. The status of these plans aren't included in...

In the trainer, when I have multiple flows and conditionals, the indentation becomes very unclear. It's difficult to track which steps link together. Better indentation and grouping of steps would help massively.

As someone who investigates a failed journey in specific browser, I want to be able to run that journey in the cloud in the respective browser using the 'RUN JOURNEY' button. A dropdown (select) with all browsers next to the 'RUN JOURNEY' button ...

As an Owner of the workspace, I want to have the capability to be able to create user groups and assign specific permissions, so that I can easily organize the users within my workspace. Acceptance Criteria Allow Workspace Owners to create ...

As QA, I want to be able filter the list of journeys, so that I can easily see what we have missed or duplicate on the journeys we have created. Right now we have 288 journeys, it's kind of hard to filter which journeys doesn't have labels or desc...

As a user I want to set a variable value from an element property, and select that element by a custom find CSS or xPath.

As a test author, I want the option to enclose a set of steps/flows in a 'for' loop iterating over provided array of values or numeric range, so that I have a single source of truth for the repeated logic (therefore one place to make changes).

As a QE, I want to be able to run specific plan or journeys by passing their ID in the deployment API, so that I can run a specific Plan or Journey. Our team is building a Test On Demand Page for the POBA's and we use the deployment API to tri...

When invastigating an error, I'm usually looking for a bug there. Unfortunately, it doesnt provide much information. It would be practical to add response body for each connection.