556 results found
-
Add support to fetch child filter summary in main filter api
Like I have filter1 and filter2, filter3 as a child filter of filter 1. If we can give a summary of filter2 and filter3 in filter1 API request.
1 vote -
Should increase Pie Charts capacity in the same tab
We use a tab for each version and there, we have a pie chart for each build from that version.
At this moment, only 8 pie charts can be created in a tab.We would like to be able to add more Pie Charts, for better visibility of all builds from that version.
Currently, we can either delete old build pie charts or create a second tab for the same version, both which are not good solutions. After each version, we send a report with all builds from that version and a guest link for stakeholders to see the progress,…
1 vote -
Should increase Pie Charts capacity in the same tab
We use a tab for each version and there, we have a pie chart for each build from that version.
At this moment, only 8 pie charts can be created in a tab.We would like to be able to add more Pie Charts, for better visibility of all builds from that version.
Currently, we can either delete old build pie charts or create a second tab for the same version, both which are not good solutions. After each version, we send a report with all builds from that version and a guest link for stakeholders to see the progress,…
3 votes -
When filter with date type field, user can select today() instead of select specific date on calendar.
I need to create a filter to collect all test result older than 4 days. Tried to filter with Last Run field but I can't see suitable operator. It must be good if we can use today() instead of select specific date on calendar or there is operator such as: Before the last X days...
6 votes -
Multiple selection on requirements
When you select the traceability of a requirement you can only add one test at a time, can we have a multiple selection like the add instances on a test run?
3 votes
Ido Tandy
responded
-
Upload a screenshot simply by pasting it to the step screen / upload screen
This will make this process more productive and easy.
Same as you do in JIRA tickets - pasting a screenshot from clipboard within the create screen, automatically uploads it to the ticket.10 votes -
Ability to expand a Requirement in the Filter Grid
It would be helpful to be able to expand a requirement from the filter view. Currently, you can see the ID, Name, Status and Actions fields (for All Requirements filter). To see the requirement description or any of the custom fields, you need to click the requirement name and be directed to another screen. Being able to expand the requirement from the filter grid would make navigation easier and allow the user to view multiple requirements simultaneously. This would be a game changer for us.
1 vote -
3 votes
-
1 vote
-
ability to add issue: fields to an instance report.
ability to add issue: fields to an instance report.
1 vote -
Allow historical users to remain in a users list field
If you have a custom field that uses the user list; only current users on a project are available. If that field needs to be set after the user has been removed from project, they are no longer available as a selection item.
1 vote -
Linked List Add New Item in drop down
Allow addition of new items to a linked list child list from the form drop down. This feature was added to regular lists a while ago and is much more convenient then modifying the list contents in the fields settings section.
1 vote -
Reorder Test Cases in Test Library & preserve the same order when generating the reports.
The user should able to reorder the Test Cases for a project in the Test Library.
My requirement:
I have 3 tests,
Test 1, Test 2, Test 3They are created in some order say, Test 1, Test 2 , & then Test 3,
But my Test 3 is the continuation of Test 1, what I actually meant is Test 3 will start from where I ended in Test 1.
So, I want my tests to be in the below order:
Test 1
Test 3
Test 2I tried several ways to reorder the tests but nothing worked.
Some of…
12 votes -
I would like there to be a way to batch delete the tests from multiple testsets
I would like to have the option to batch delete all the tests within multiple TestSets. Alternatively, if I clone multiple TestSets, I should have the option to delete the tests within the new cloned TestSets
1 vote -
link requirement to requirement
Ability to link a requirement to another. This can be another option in Traceability tab where we currently link tests and issues.
7 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…
31 votes -
create a way to filter/report on issue status history
I am looking for an easy way to report on the status history of an issue. As it is now, I can only easily filter on current status when I create reports/filters. I am looking for a way to find issues that were ever in rejected status or were at one time set to "reopened" without having to manually read the history of every issue.
1 vote -
Task Board - Customize with chosen fields
I would appreciate to be able to choose the fields shown for all tasks. For exemple, to be able to see the Priority or other chosen fields.
10 votes -
Only display step information that failed when creating a bug using JIRA integration , do not include all steps
When creating a bug using JIRA integration currently all steps in the test are pased into the jira description. It would make more sense to only paste the step that failed and the results from that step. this would give the user the information on the actual issue and reduce the amount of editing currently required using jira integration
3 votes -
9 votes
- Don't see your idea?