BillW
Occasional Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Re: Add an option to 'Exclude Inactive Releases' in Reports & Legacy Reports
We've had QAComplete for a few years now and the number of inactive Releases continues to grow. As such the number of complaints I get from our QAComplete users having to scroll through all of those inactive Releases when generating a report is growing. Seems that adding a feature to exclude inactive Releases in Reports and Legacy Reports wouldn't be a big deal so how about it? Thanks2.1KViews0likes0CommentsAdministrator option to push list screen layout to all Users
It would be great if there was an option for Administrators to push list screen layouts for each applicable section (Releases, Requirements, Test Library, Defects, etc) to all our users. Right now this is dependent on the user who likely won't take the time to do this. We're an On-Premise customer and we recently upgraded from 11.7 to 12.0. Following the upgrade I distributed a suggested column layout for these pages but like most of my emails, it was mostly ignored. If instead I could push out my suggested column layouts for list screens, I think our QAComplete users would have a better grasp of what they're looking at, as well as utilizing some of the columns that are so helpful with linking (e.g., #Tests, etc). Thanks544Views0likes0CommentsRe: Add an option to 'Exclude Inactive Releases' in Reports & Legacy Reports
I want to run a Requirements report in Reports or Legacy Reports, for a specific, active Release. There isn't an option to exclude from the Releases drop-down list to exclude inactive releases. Sure would be nice if that feature was available.2.8KViews0likes0CommentsRe: Move implemented ideas off the "Approved for Discussion"
Every so often I check the QAComplete Feature Requests page to see if any of my feature requests, or others I've kudo'd, have been implemented and sadly, none so far. However I have seen a few in the "Approved for Discussion" catagory that I believe have been acted upon so why not move them off to the Implemented section? Here's a few in the "Approved for Discussion" section that I think might qualify: Remove unnessary "Required" field (work phone) Add Releases tab in the Test Library Update/Modernize the UI Reduce the size of the SmartBear banner & Customer company logo box Lastly, myself and many others have submitted New Feature Requests from as far back as 2015 - and yet they're still being discussed? If these requests are actually being discussed, that's fine lease as is but if not, why not pull them off onto another category (Undecided or Not Considered for Action, etc) and list what's really being discussed/considered? Thanks!1.7KViews0likes0CommentsAutomatically Re-assign a Defect to the Owner when Status is set to "Resolved".
At the time the Status of a Defect is set to "Resolved", I'd like to have the capability (via an Escalation rule or Workflow) to reset the value of the "Assigned To" field back to the Owner of the Defect. Right now this is a manual process which we often get complaints about. Users ask why the system can't populate the "Assigned To" field programmatically. I could accomplish this via the Escalation Rule or Workflow if the value of the Defect Owner was included in the list which unfortunately it isn't.712Views0likes0Comments