Ability to have custom field dependencies/relationships based on selection of a dependant field
Ability to have custom field dependencies/relationships based on the "Item" selection of a another custom field. i.e. Custom Field "Phase" --> Item selected = "Requirements" Custom Field "Type of Defect" dependent on the Custom Field "Phase" selection of "Requirements" --> Items available to select "Spelling error", "No Requirements defined", "Does not meet requirements" In the above example, the Custom Field "Type of Defect" would display different Items depending on what was chosen from the "Phase" Custom Field. thanks
Allow Admins to close reviews
Bringing back an old thread - I'd like anyone with Admin privileges to be able to move a review to Completed. We've had several instances where someone has left the company, or is on extended leave, and their roles is required to move a review to completed. On solution is to shuffle roles - while that will allow a review to close, it's "not right". If the author of a document is out sick - yes I can assign the author role to someone else - but now you are fudging the review records in order to get the closure. Later when an auditor comes in we have to give a song and dance as to why the roles in the review don't represent the actual roles the staff members have. We shouldn't need to alter the records to move things forward. The review is more than a record of defects - it's a record of who did what, and we shouldn't need to compromise that to get around a technical glitch.
Capture for Jira_ Issue Template: cannot save all fields
Hello, when trying to create a new template for creating Jira issues, some fields are not saved such as Sub-Project(s),Labels and testing phases. Also, I cannot update the template afterwards. Do you know if this is a known issue or if there's any existing workaround ? I'm getting crazy updating manually all tickets... Thanks a lot! Nathalie
Arrange the fields in the review according to our need
Hi, Would love to have the capability to order the the fields of the Review in the Review page. For example - I have a Review custom field that needs to come right after the 'Deadline' field. So the capability to move change the order of the fields would be helpful. Thanks, Puneet.Notification template for "List Review Stalled Author Not Reworking" is incorrect
Hi, The notification template for "List Review Stalled Author Not Reworking" is incorrectly assigning defects to non-authors. The template looks like this: subject: Review #${review.id}: "${review.title}" is currently stalled waiting for ${user.name} body: Review #${review.id} has defects that need to be fixed by ${user.name} and verified before the review can complete. Created: ${review.datecreated} by ${review.creator.name} Deadline: ${review.deadline} Workflow: ${review.workflow} Defect Log: ${review.defectlog} Looking at the substitution variables docs and the notification template docs, the var user.name should be review.author.name (see vars here: https://support.smartbear.com/collaborator/docs/server/admin-tasks/variable-substitution.html). The description of this notification template also supports that it should be the author that is responsible for defects and is being waited on, not the other users (link here: https://support.smartbear.com/collaborator/docs/server/settings/notification-templates.html). Notification: List Review Stalled Author Not Reworking Sent to: All review participants and recipients of the notification list emails. Remarks: Indicates that the review is stalled because the author needs to fix some defects. This was issue was pointed out here previously, but the topic was closed without action (https://community.smartbear.com/t5/Collaborator/Reviewer-gets-e-mail-prompting-for-defect-fixes/td-p/107761). This appears to be pretty cut and dry and I would expect this to be fixed in an upcoming release. This issue was noted in 9.2 in the previous post, and we are on 11.5.11506.
Log all activities of users and admins in Collaborator
In a Large enterprise there will be multiple admins. To track who has done what, Admin should be able to get the log of all users activities. Like, Disabling and Enabling review templates, Disabling and enabling users or adding users etc. In simple terms a log should be generated for every activity happens in Collaborator through all the ways. ex: GUI, API, Collab client, Thirdpart clients, Commands etc.
