Shared steps are very useful and i propose will be a lot more if we could parameterize them. For a piece of data thats required in the shared step can be named as a variable/parameter which can be specified a value either in the test case or during test run time. This will make the shared steps way more reusable and us QA Engineers a lot more productive.

When sending results of the automated executions, there is no way to assign a result to a specific parametrized version of a case if it had parameters set. It would be great to have a possibility to submit results against each parametrized version of a case, if it has parameters set.

After resolving a defect, an option to set all the related test cases in test runs to Re-test would be very useful.

It would be great to have an option to use shared steps not in just one project, but choose multiple projects to use it in.

It would be good to be able to select test cases from multiple projects when creating a Test Run. Most companies have multiple apps/api's/website, and having them in different projects doesn't allow for you to create 1 Test Runs which covers them all, especially for regressions tests which impact multiple areas.

When navigating the repository, it would be nice to have more contrasting highlighting of a) suite that is selected in the suite tree, and b) a case that has been selected on the screen

As A QA I Want the ability to see the tests that I want to run for a Jira Story and see the test status So That I can share my progress with others