Feature Requests & Ideas

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 a user I want to know which exact output page I need to open when a build fails in the CI pipeline so I can find back what the exact cause is. Currently I only have an url of the version page of the journey but that does not give me the exact r...

Currently when running the trainer in incognito the window will not close and open another mabl tab. It would be nice to have the window close when you save to allow you to go back to the active mabl tab.

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...

A more detailed list of crawled links. So the report will show: - Links crawled - Highlight broken links - Attach a screenshot of the error - List why the link was tagged as broken (eg. 404, 504 etc)

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 ...

Instead of the current way of adding journeys when in the Add New Plan screen (Add Journey > Type title), it would be better for its behavior to be like the Journeys page where I have the journeys on a list table so I can filter by label,etc. a...

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...

When a journey is in a plan with multiple browsers (e.g. chrome and firefox), I want to see the journey run as failed when it doesn't pass in both browsers, so that I'm not being misled to think everything is smooth.

I want to be able to group journeys in test suites (and nest suites within one another), and use test suites (not journeys) in test plans, so that I can operate on proper level of abstraction. Test plan as a concept is meant for (among other thin...