I want to be able to give certain team members permission to edit picklists on only some fields ? eg) we have a custom field 'Run on Build' that we want all team members to be able to add values to, but don't want them to be able to have general access to edit values of all other fields

e.g. I have created one Custom View as 'View1' which has several child custom views such as 'View1.1','View1.2'. Now i create another custom view below 'View 1' as 'View 2'. Having the ability of simply copying 'View1.1' and 'View1.2' under 'View 2' would save lot of efforts for users. Especially if you see your project having number of similar tasks being created under it repeatedly.

When clicking on Reorder Steps for a Test - the steps appear as a long list without the Step Number next to them. This makes it hard for the User to know which Step to swap around. Please could we add the Step Number to the title of the Step.

Have the ability to copy a filter within and across modules.

Sometimes we include the same test case a couple of times in one test set, but with different parameters. Unfortunately now we must edit those parameters one by one - and this is a lot of clicking.
I can see 2 solutions:
1) Allow modifying parameters directly in test set table
2) On parameters screen differentiate parameters by test case instance/number

I am exploring the open source Automation tool Katalon Studio for automating test cases for mobile and web applications. I would greatly appreciate if Practitest can provide 2 way integration with this tool.

Please add the option to undo when removing step by mistake.

If you are using hierarchical requirement, make the status of a parent requirement be the aggregation of the status of it's children.

Dashboards and reports should be able to be created to report on multiple projects. If an organization is able to report on all the activity within Practitest, it will allow Executive Leadership the ability to see the entire workload of what is being processed via Practitest.

It really will show the immense activity accomplished during testing as a whole.

When there is a problem / something unclear with a test, the author is addressed for explanation.
The author is not conserved when cloning tests (example - when moving tests from one project to another), causing a lot of confusion as to who should receive the questions. The cloner is listed as the author.
When cloning tests, i can choose which attributes of the test i want to import to the cloned test (version, status, componenet, etc). Author is listed but cannot be selected. Please add the ability to import that as well.

I use parameters both to allow for flexible test reuse but also to help identify which portion of an app I'm testing, when different sections are similar. In some cases, this would allow me to use a parameter in the test name instead of in every step of a test.

It would also help with JIRA integrations where the specific section (defined as a parameter in the title) would automatically be added to the issue ticket summary field during the 'Fail & Issue' process.

It would be utmost useful to be able to see any comments devs make in Jira on a bug so that Qa can see it in Practitest. Not just name, description and status.

At the moment the 'Save Changes' option is a default one, we would like to have the 'Save & Close' as default within our account. Can you add an option to enable this per account?

I would like to link a particular testset execution result to Jira ticket.

Make it possible to show the JIRA status of a story which was imported using the JIRA plugin. for example, if a story is accepted on JIRA, we should see this updated in the practitest requirement