561 results found
-
Versioning test cases
Feature to versioning of test cases, allowing comparisons of differences and return to previous versions.
74 votes -
Github with Two-Way Integration
Please add two-way integration with Github. Not everyone's on Atlassian products such as Jira, Bitbucket, et al.
45 votes -
execution progress graph with costume fields
We would like to have execution progress graph displaying custom fields.
example:
a execution graph with ("automated", "planned for automation",...) fields.45 votes -
make requirements links visible when executing a test
When executing a test case one of the key things you'll want to reference are the requirements, so logically they should be accessible.
33 votes -
Include pictures / attachments in reports.
It would be nice if there was a way to include photos and attachments that are included in test in the final report for reference. It can be odd at times to have a test that references a picture or attachment and it does not show up in the report.
32 votes -
Ability to sync the comments from requirements and bugs from ADO to PractiTest and vice versa
Currently when the requirements and bugs are synced from ADO, the comments are not synced.
For requirements the comments have valuable information reflecting the changes and doubts which are important for a tester to know while creating test cases so it is very critical to include the comments as well.Also if a tester has certain doubts on a requirements if there is a 2 way sync he can just post the comments on the PractiTest and they should flow to the linked requirement card in the ADO.
For bugs, since the developers won't always have access to PractiTest, the will…
28 votes -
Ability to add a test case to a test set by writing the test number/range
As mentioned with the Ability to add a test case item, we tried filters; it’s cumbersome to have to shift gears and create a new filter every time that we want to look up / search for something new. It clutters things up as then there is the maintenance and scrolling to contend with as well.
26 votes -
Add requirement link to an issue when posted to Jira
When an issue is created from a test, the associated requirements could be linked (if Jira requirements, then the Jira requirement link) to the issue document (perhaps appended to description, or to a field defined in Practitest by the user) before being sent to Jira.
Why? So in Jira a developer can click straight on the requirement to see what should happen, rather than dig through a number of screens to access the requirement26 votes -
Project/Admin‑Controlled Project‑Level Column fields Configuration for Test Set Instances
We are requesting an enhancement that allows Test Set column configurations to be managed at the project level, rather than being limited to individual user settings.
Currently, column visibility and ordering can be customized only at the individual Test Set instance level, and these settings apply per user. While a “Reset All” option exists within a Test Set, it also operates at the instance level and is not governed by project‑wide controls.Why this is needed:
Test Sets are frequently reviewed by senior leadership and cross‑functional stakeholders. Many reviewers may:
1)Be unaware of column customization features
2)Configure columns differently (or…24 votes -
Have option to add field or custom field to an item in dashboard
I'd like to have the option to select fields in items displayed at the dashboard.
Example, if i have custom field of priority/severity, i'd like to be able to add it to the items displayed at the dashboard item.
To be more specific, if i add an item with "Test" entity and "latest" item type, i'd like to see the test priority as well as the existing fields in the table23 votes -
Adding filters to Dashboard tabs for easy navigation
Description:
Currently, dashboards are presented using a tabs‑based structure, which requires significant horizontal scrolling to access older dashboards. As the number of dashboards increases over time, this approach becomes difficult to manage and navigate efficiently.
This is inconsistent with how other PractiTest entities—such as Test Library, Requirements, Issues, and Test Sets—are managed using filters instead of tabs.==>Proposed Enhancement
Introduce a filter‑based mechanism for dashboards, similar to existing filtering functionality across other PractiTest modules.==>Example filter options could include:
Year (e.g., 2025, 2026)
Team
Project area
Owner / Creator
Status or reporting categoryUsers could easily filter dashboards based on…
22 votes -
Sync attachments from ADO to PRactiTest and Vice Versa
Currently we are not syncing the attachments from ADO requirements or bugs to PractiTest nor from PractiTest bugs to ADO. It would be great if we can do a 2 way sync for the requirements as well.
Many times the big requirements have attached docs which are essential for a tester to see to create test cases.
Bugs in ADO will have screenshots and log files attached and they need to sync across to the PractiTest as well.
Also when a bug is created from PractiTest to flow thru to ADO it will/should have screen shots attached along with other…22 votes -
Test case templates
Allow creation and selection of test case templates. These could have standardized titles, step names, etc. Example:
Title: "My App: <component>: <test>"
Step 1: "SETUP"
Step 5: "CLEANUP"20 votes -
Ability to get all filters for a project through the API
We need the ability to get all filters for a project through the practitest test API. Currently we are trying to use the API to generate an internal report based on test sets in a test filter.
We can filter the test sets by the filter-id but we have no way to prompt the user which filters are available to generate the report on.
Maybe something like:
https://api.practitest.com/api/v2/projects/YOUR_PROJECT_ID/filters.json19 votes -
Allow the account admin the ability to create reports/dashboards across projects.
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.
19 votes -
Conditional Mandatory Fields - If I have a field that is value X, then make one or two ther fields mandatory to fill in (or select).
Conditional Mandatory Fields - If I have a field that is value X, then make one or two the selected fields mandatory to fill in (or select). If value is not X then either grey out the fields or make the other one or two fields not required.
18 votes -
Able to create a single dashboard across mutiple projects
Would like to have a single dashboard that can cover multiple projects. As a manager of projects this would be highly benefitcial.
17 votes -
Include comments in the PractiTest API
Include comments in the PractiTest API.
17 votes -
Add new value to standard or custom fields via API
In a context of automated test, it could be valuable to be able to append new values to fields already existent via API.
At the moment, we can only replace the entire Field with new possible values. And if something goes wrong, I feel like there's a high chance to lose information.
17 votes -
clone or copy views in the tests library
For example we have a view with a lot of child views and now We would like to create the same view but with a different parent filter. So we would like to clone the existing tree and modify it instead of creating it from scratch.
17 votes
- Don't see your idea?