Feature Requests & Ideas

As a QA Engineer, I want to have an ability to duplicate plans, so that I can easily create new plans without reconfiguring everything. Current Use Case: on our project we create separate plans for Prod and Lower environments. The only differe...

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

When creating a JIRA ticket from mabl, the creation fails because some custom fields(specifically the mandatory ones) are not proposed/field. To workaround this, I have to create another type of ticket (task, ER or other) that has no mandatory ...

As a QA Manager, I would like to be able to look at the Plan tab and set the plans in a specific order that stays when I return to that page and can be changed and set again as needed. It would also be helpful to be able to lock a filter view also...

I would like to be able to do an Else If statement. It would make it easier instead of having use nested If statements to check multiple items in my test case.

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

I would like to be able to have a filter for plans on the result page.Currently the By Journey tab does have a filter. I would like a filter on the Plan page as I would like to be able to see at a glance and compare certain test plans.This would h...

As a customer of mabl I would like our solutions to trigger and view the results of mabl plan runs via Azure DevOps. Similar to how existing integrations made for Jenkins and Bamboo uses this. Link: https://docs.microsoft.com/en-us/azure/devops/e...

As a QA engineer I want Mabl to support drag and dropping like in a kanban board so I can test these functionalities as well.

We have mabl-jenkins integration, where jenkins triggers plans after deployment. The problem is that we have one robust plan with several journeys in it.So currently when 1 journey fails, the whole plan triggers again with all the journeys, the pa...