Showing ideas with status Selected for Development.
Show all ideas
Status:
Selected for Development
Submitted on
11-17-2022
04:57 AM
Submitted by
ga1
on
11-17-2022
04:57 AM
If I write a comment on a review and later want to delete it, I click the Delete button to do so. The message which then appears looks like the image below: So I have to click Confirm if I want to cancel, and Cancel if I want to cancel the cancellation; i.e. I don't want to cancel the comment. I think. I think it would be a lot clearer if it used the word "Delete" instead of "Cancel", so could say "Are you sure you want to delete this comment?", and had Yes/No buttons, such that Yes deletes the comment, and No doesn't.
... View more
See more ideas labeled with:
Status:
Selected for Development
Submitted on
04-28-2017
12:33 PM
Submitted by
rwilkinson
on
04-28-2017
12:33 PM
User experience would be greatly improved if the reviewer could associate their comment or defect to a range of lines instead of just a single line. Additionally, if that range could also be inclusive of characters within a single line that would also be appreciated. When comments or defects are part of a large block of code being able to accurately call out an area of code instead of just a top line of code is helpful.
... View more
Status:
Selected for Development
Submitted on
04-15-2015
08:17 AM
Submitted by
ncianfro
on
04-15-2015
08:17 AM
Very frequently comments are added in a review that need to be converted to defects. The "ADD AS DEFECT" button is used but the defect text is blank. In this use case, the comment is the defect. This requires manual copy/paste, restating the comment, or adding a description of "see comment". This product enhancement request is to pre-populate the defect text box when converting a comment to a defect. This would steamline upgrading comments to defects.
... View more
Status:
Selected for Development
Submitted on
05-27-2015
07:23 AM
Submitted by
JakeSwart
on
05-27-2015
07:23 AM
In the chat box of file foo.cc I would like to reference a specific line in file bar.cc. For example, I have bar.cc:line 12 written in my code collab chat box. In this case, code-collab only recognizes and allows the jump to bar.cc, but not to the line. I would like a feature where a designer can write a reference to line 12 in bar.cc and Collaborator automatically auto-links the to the correct line.
... View more
See more ideas labeled with:
Status:
Selected for Development
Submitted on
03-30-2015
02:20 AM
Submitted by
tcecb
on
03-30-2015
02:20 AM
When you have a review with many files and many comments on each one, it would be nice to only see the files that you still have to review. On the "Review Materials" section, could we have a toggle button that would hide/display the files that the current user has accepted and that haven't changed since? In that same section, could we also have a way to hide all the lines that the current user already approved (and that didn't have any activity after the approval)? That way, for files with many comments, you would very easily find the ones you should review. This is slightly different from the current highlighting which is already quite good.
... View more
Status:
Selected for Development
Submitted on
04-10-2015
04:44 PM
Submitted by
hyltonr
on
04-10-2015
04:44 PM
On large reviews, it can be hard for a reviewer to track which files they've completed reviewing, if there are defects or discussions still ongoing. In that case, you don't want to mark the file as accepted, so it would be nice if there was a "Review completed for this version" button or flag.
... View more