28 results found
-
0 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 -
0 votes
-
0 votes
-
0 votes
-
Ability to resolve comments with indication who resolved them
Ability to review similarly to Word (Add comments, tag, suggest edits, resolve/reject suggestions)
0 votes -
Reorder a group of instances in one click
Right now I can drag one instance and move it to another place in the instance list in the test set.
I'd like to be able to check more than one instance, and then be able to move it to another place in a grid altogether2 votes -
Add Test to the Testset inside the test itself
When I'm in the Test, I might decide immediately to add it to the Testset/create a new Testset with it.
Now I need to go back to Test library, select this Test, then click on "Create a Testset"/"Add to existing Testset" buttons.
This is too many clicks, I want to decide whether I want to run my test or not when I'm inside this test.3 votes -
2 way integration with Azure Devops (ADO) Server doesn't exist
Currently we can create a 2 way integration with Azure Devops, but only if Azure is on Cloud.
The integration with Azure Devops Server doesn't work.3 votes -
keyword search loses many test cases
When I enter a keyword and search, many test cases with the keyword will not show.
Now just crtl+F for every page and it is miserable...9 votes -
When cloning a new project, add an option to clone filters
Right now when you try to clone a project from Account settings, you have 4 options:
clone fields, clone users, clone user groups, clone integration settings.It would be also very useful to clone filters. Probably should be related to "clone fields" option
14 votes -
Adding more fields to panel with PractiTest data in Jira ticket
I'd like to see more columns displayed in JIRA when the linked Tests from PractiTest are displayed - or Steps of a run if it's a bug.
For example, for linked Tests:
- Assigned to
- Tester (of a last run)
For bugs
- Priority (if it's different in PractiTest)13 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 -
9 votes
-
Include comments in the PractiTest API
Include comments in the PractiTest API.
17 votes -
In The Task Board As Well As Filtering by Person why not filter by TestSet Filter & Test Filter -
That way you can multi purpose it for multiple test runs.
I general we should add the option to filter according to certain fields
15 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.
38 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.
46 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.json18 votes -
Add the ability to add custom fields and modify columns for Test Instances Run History
Right now, we only have:
- "Run date"
- "Status"
- "Tester"whenever we look at the test run history for instances. It'd be neat to have the option to add custom fields so we can better track previous runs.
For example: I want to be able to add "Commit hash" and "branch" to test instances run history so I can see the last GitHub commit that was tested.
7 votes
- Don't see your idea?