General

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Extend width of column on Requirements when adding from a Test script

    Our Requirements all start with 'As a user I want to be able to...' and this is all that is shown as the column isnt wide enough to display the whole requirement. A hover over the requirement to display the full name would also resolve this issue.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Please improve Assembla integration

    We purchased PractiTest with the assumption there is a one way integration with Assembla. We have had to turn this off as it creates more manual work for our team.

    Please could you address:
    -When Assembla ticket is updated so is PractiTest
    -Show Issues that have been created and linked to Assembla

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Ability to Select Range by holding down Shift Key

    I would like the ability to select a range of Tests by holding down the shift key and selecting the first and last item. This would really improve my productivity when working with large numbers of tests.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Set requirement filters when importing from Jira

    Set requirement filters when importing from Jira
    The ability to set filters on requirements when importing from Jira. Currently a new requirement/s can be imported from jira. The requirement/s join a large list of requirements until the user selects and completes a batch edit on the requirement/s to assign filters. Using filters in the requirement tree allows for quick location of all requirements relating to the filter. I propose that practi-test gives you the option to set the filters when importing. improve the import screen to provide a screen similar to the batch edit when importing allowing the user to…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. I would like to be able to sort test cases alphabetically when adding them to a test set.

    My test cases are named based upon area of application. So when adding to the test set I am manually sorting through 50+ test cases per section which I need in chronological order for execution. The ability to sort test cases alphanumerically when adding so I can add them in order by section would be huge for me and my team.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Make it possible to change the 'test set' on a run test instance

    Add the ability to change the 'test set' that an instance of a test is in, once it has been run
    We have some test instances which have been added & run in the wrong test set. We want to move the run instance to a different test set, , for reporting purposes., but not loose the results and run history

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Close test runs

    I would like to have the possibility to close a test run so that we cannot change the results.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Improve Jira Integration

    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)

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Synchronize PractiTest fields with JIRA fields (field mapping)

    There are several fields in JIRA that we need to be reflected in PractiTest. In particular we use a fix in version field to associate releases in Jira and we need that field to be updated in the corresponding PractiTest ticket. Other fields such as priority should be mapped and synchronized.

    We spend a copious amount of time with each release/sprint updating Requirements in PractiTest to reflect what the PMs have assigned for the current development cycle. Each time a requirement falls out of scope or a new on is added, we have to manually update PractiTest.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow WYSIWG input - currently if you cut and paste requirments, test cases, etc, you get erroneous characters in the text.

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

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Issues

    Creating an issue in JIRA should take more than 1000 characters(This should include all steps from test Set in PractiTest)

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Propagate Test Set Fields to the Test Case and Related Issues Instances

    Example: System Version (1.0, 2.0, 3.0) custom field added to the test set. If I want to compare the results of all test instances for each Test Set execution based on this field, I need to have that value that I would enter into the Test Set automatically populate any tests in the set, and any issues that are created in the execution. Right now you have to bulk change the test instances with the System Version in order for them to show up in dashboards.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Hi,

    Kindly note that we started to implement the feature you requested and now it is already available within tabular reports in our new Reporting module where you can take values from Test Sets while generating Instance reports hence you don’t need to manually batch edit instances.

    In addition we plan to implement this feature to the dashboard graphs and will keep you updated.

    Thanks
    Christine

  14. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add JIRA syncing of story status

    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

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. enhance 2 way integration with Jira

    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.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. 2 way integration with GitLab would be a nice feature.

    Many companies use GitLab and they would warmly welcome a 2 way PT integration. At our company we conclude projects. One is developed in Redmine, the other is in GitLab. It would be nice to use PT for both platforms with equal funcionality.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. adding attachmant to a test set

    once you have a test set deriving from the main test, i need the ability to add an attachment to the test set.
    you can add one to the main test but that won't help.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

General

Feedback and Knowledge Base