MaryConti
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Add a capability to tag another user in the comment box
Sometimes, you want a different person to look at something, or respond to a comment. My team would like Collaborator to have a capability to tag another user. For example, in Jira, you can use "@lastname,firstname" to tag another user. We would like a similar capability in the comment boxes.13KViews26likes2CommentsPlease provide a detailed report for a review that contains timestamps of state changes.
We would like to do some metrics around how long a review stays in each state. The information to do that does not seem to be available anywhere. Please provide a detailed history report that shows all changes to a specific record. This would also be helpful in debugging issues.2.5KViews5likes0CommentsRe: Fix the diff viewer and marker issues
Currently, I have a review of a word doc with 6 versions uploaded. After one upload, the markers move to a different section of the doc and stay there for later versions. The doc has had a number of smaller changes, but nothing significant in the areas where the markers are wrong, except whitespace. The markers after that seem to be OK, too.4.4KViews0likes0CommentsRe: Easier Way to Differentiate Between Updated Files
It should be easy to see the changed files from the main review screen. A column that indicates changes from one version to the next in View As Separate, and the same column can show "changed since previous upload" in View as Overlay".6.7KViews0likes0CommentsMake field mandatory by checkbox, not by Due By or other non-obvious criteria.
This issue came to my attention when I found that the Participant Custom Field Multiselect box is always mandatory. It doesn't matter if you have Due By/Visible By set to a value or not. If you are using it, it is mandatory. That is not how I want it to work. I have seen something similar on other fields where you put in validation, and it makes the field mandatory. I don't necessarily want it to be mandatory, but if it is used, it should follow a certain format. I would like to be able to specifically define if a field is mandatory or not. It could be visible and not mandatory, visible and mandatory, and it may or may not have validation or selections.1KViews0likes0CommentsParticipant Custom Field as Multiselect list -- mismatch between documentation and reality
I tried to implement a Participant Custom Field as a Multiselect list, and the documentation says this: Multi-Select List. A drop-down list of pre-defined choices. User may select zero, one, or multiple values. However, when I implement this, the user is required to select a value. Is this a bug? Or is the documentation incorrect? (I hope it is a bug. I do not want this to block reviews.) Mary1.2KViews0likes0Comments