Mention and Notify User From Review Comment
I would like a way to indicate to another Code Collaborator user that a comment I've made requires their input and notify them specifically about that action item. In several tools including Jira, Azure DevOps, GitHub, GitLab, and others (including this form, apparently), you can type "@[user name]" where "[user name]" is the name or nickname of another user and that user will be directly notified that they have been mentioned in a comment. The use case I have for this is to expedite communication in conversational comment threads. Sometimes I may have an idea for a change or issue in a review, but I want feedback from another user with relevant experience, so I would mention them to indicate I'd like their input. Currently, I can poke the user, but then they don't have any context for why they've been notified. Ideally, a mention system would search based on display names since our SSO setup requires login names that look like random text. An autofill system would make using this feature much easier. Additionally, having some marker on the website that indicates where you've been mentioned would be useful.2.3KViews2likes3Commentsinclude assignee from defects in action report or at least on reports
We utilize the assignee field on defects to drive action items. However, we have not been able to find a way that this is communicated in any method outside of the actual review. Having this on the home page and/or notification activity (tray, in app, email) would help to expedite action.1.3KViews0likes4CommentsPlease add ability to set business days/hours for email notifications
On the same subject ashttps://community.smartbear.com/t5/Collaborator/Fine-tuning-email-notifications/m-p/99727, it is really annoying that if a reviewer hasn't completed a review by friday afternoon, they return to their computer monday to dozens of reminder emails. It would be nice if you could configure business hours/days and you would only get one reminder (regardless of your stalled review timeout) on return to working hours. So if business hours are 9-5 and you haven't finished a review, and your timeout is 2 hours the next morning instead of having 8 emails you would have 1.1.1KViews0likes0CommentsNotification 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.999Views0likes0CommentsLog 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.979Views1like0CommentsReturn email address when user is in a comment
We recently upgraded to rev 13.4. In this new rev of Collaborator (we were previously at 10.1) there is the ability to email a user if their name is used in a comment. The problem is that in the email the user receives there is a link back to the review their name was used in. The link is missing part of the upfront URL and as such will not take the user to the review. I am guessing that it is a configuration that was missed on install. Please advise. THANKS!Solved958Views0likes1CommentCollaborator URL in participant notification message
After creating a new review, participants are notified via an email message stating, "Select this link to display or participate in the review: <URL>" In our environment, at least, the URL seems to be a loopback and does not take participants to the actual review package. Is there a way to configure the outgoing notification email so that it contains a link to the actual review?Solved882Views0likes1CommentAbility to disable automatic changes of review progress on Action Items list
Our workflow is such that we want to clearly define when control of a review moves to a different participant. For example, I create a review and annotate it, and then move it to the inspect phase. The review progress then appears in my action items list (and on the system tray window) as "Waiting for comments". However, as soon as the reviewer makes their first comment, it switches back to Perform, which is a nuisance since frequently the reviewer is still working on the review - they may find that a later file answers a question they'd asked, so they go back and delete an earlier comment, or edit one. The result is that I start responding to a comment which then gets updated or deleted by the reviewer, who isn't expecting me to have resumed work on the review since they haven't yet clicked "Wait". It would be nice to have an option whereby Collaborator will leave the review progress as it is until the "Active" participant(s) click "Wait" to wait for further activity. This way, the reviewer can add/edit/delete their comments, approve files etc until they're happy that it's ready to pass back to the author, and only then have the author notified that it's ready for them again. Similarly, when the author then responds to the comments, the same functionality would prevent the reviewer from being asked to respond to the comments until the author had finished writing them. This would not need to prevent participants from participating at any time, as it is very useful to have this ability - it would just prevent one person's changes from causing other participants to be notified and the review progress on their action lists to change.798Views2likes0Comments