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

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

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.

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

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

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

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.

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.

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.

It would be nice if we can get the detail of a comment by API or Webhook.
Right now it seems possible to get the update on a comment by Webhook, but not in detail.

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.

Allow the cut and paste of information from Word, Excel or any othe non-8 bit editior.

We think the following would improve the Jira integration tremendously if implemented:
- In the auto generated issue description (when clicking fail & issue) include the expected result

• Make linking existing issues less cumbersome. At the moment users need to:
  1) Add the ID
  2) Navigate to the issue
  3) Edit it with the pt_id
  4) refresh in the step
  This should all ideally done by PT (itself + the Jira plugin)

• Full 2 way integration: add a tab in Jira that lists hyperlinks of all the linked PT tests (other tools such as QMetry do this)