ContributionsMost RecentMost LikesSolutionsAdd option to edit test outcome for a completed test run After a test run is completed (all steps marked either pass or fail) its outcome gets locked and can't be altered. While the reason behind its logic and needed, adding the ability of changing test outcome depending on access level (admin/lead access only) would allow more flexibility and would help in situations like: Several test runs are completed as failed due to an issue that was overlook and in the end not an issue. This mistake can not be amended and a new run is required, which will then require more work when extracting metrics etc. Test outcome should be editable as long as End Run button was not pressed. Re: Force User Log Off No ideas are tagged as Accepted for Discussion or Selected for Development. Any place where we could get some hints on what's currently under development? Re: Collapsible Folders/Directory Trees Completely agree, this is crutial to implement. +1 This extended folder estructure is a great obstacle when it comes to organize a large amount of folders and subfolders. Re: Add ability to clone release It's a good improvement for the future. +1 Re: Speed up linking of tests to configurations A "check all" button is much needed here. Any technical reason you guys didn't implemented yet? Add ability to customize Test Runner layout Test Runner screen is one of the layouts can't be customized at the moment in the app. In addition, the default view of pre-set fields does not allocate much room for some fields like, worth case for us, Title (test case name) column. For manual testing it requires to always resize this field prior execution and changes aren't save after window is closed. In a big organization, with a large amount of test sets per QA, going through these few clicks can definitely result in a real time waster. As discussed here: http://community.smartbear.com/t5/QAComplete-Feature-Requests/QAComplete-add-the-Priority-of-Test-Cases-to-the-Test-Runner/idi-p/98369 We looked into providing a "screen layout" for the test runner and it proved to be a larger issue than we expected. 1) Is this feature in development or dropped? I can't find a related ticket to Kudo it. 2) Would it be possible that changes in size/length of fields are kept after the test runner is closed? So that opening a new test runner screen will display exact setting of previous screen.