include 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.3KViews0likes4CommentsRework what is "Action items"
Right now, I get an action item when a review moves to Inspection and I'm the inspector. That's fine, but once I send it to rework, I don't want to see it again until its back at Inspection. Right now though if the author uploads new reviews, it shows back in my Action item list. Likewise Inspectees will have their review show as an Action Item while its still in the Inspection phase. For larger reviews this is a problem because they'll start uploading new revisions while I'm still conducting the review. Both of these result in confusion for my team.306Views0likes0CommentsCustomize generated email
When attempting to notify users via email, the generated email only has the review id and not full hyperlink. For example,ui#review:id=XXXX would be provided and not a hyperlink in said email, but nothttps:/reviews.domain//ui#review:id=XXXX I'd like to have a feature that could allow us to add the full link to the generated email481Views0likes0CommentsMention 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.3KViews2likes3CommentsUse display name in user tagging
User tagging (COLLAB-3321) is a great addition, but when it displays tagged users as their login name, it's hard to use with SSO. With my company's SSO service, the username value is a long, cryptic string that uniquely identifies users, but users never see this name in normal use of company systems. Our users update their display names to show their actual names and it would be helpful to show this value instead of the SSO ID assigned to the login field.780Views0likes0CommentsAbility 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.798Views2likes0CommentsAdd 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. Or you would have one email on Monday morning versus dozens for a review "stalled" over the weekend.791Views0likes0CommentsLog 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.979Views1like0Comments