Showing ideas with status Accepted for Discussion.
Show all ideas
Status:
Accepted for Discussion
Submitted on
07-23-2015
08:43 PM
Submitted by
carol_t_price
on
07-23-2015
08:43 PM
Add more options other than "Marked Fixed" in Collaborator. Marked Fixed can be confusing. Options: Mark Fixed Mark Closed Concur with Reject Concur Withdrawal
... View more
Status:
Accepted for Discussion
Submitted on
07-02-2015
01:03 PM
Submitted by
MGergely
on
07-02-2015
01:03 PM
on
07-02-2015
01:03 PM
Edit Defect / Comment box falls off the bottom of the screen when the item you are entering is near the bottom of the page. This could be easily missed and if not missed requires user to scroll down the page in order to take required action. Change the window scroll point to ensure the comment/drop downs are specified when creating the defect (not the best screenshot below but close enough).
... View more
Status:
Accepted for Discussion
Submitted on
07-02-2015
12:58 PM
Submitted by
MGergely
on
07-02-2015
12:58 PM
on
07-02-2015
12:58 PM
The comments are not easily distinguished from each other. Create a space or highlight more clearly the comment/action that is currently active. Can we add some sort of delimiter/space to separate bug comments?
... View more
Status:
Accepted for Discussion
Submitted on
05-20-2015
06:21 AM
Submitted by
FSC
on
05-20-2015
06:21 AM
Hi! We encourage our employees to add a version to a PDF or DOC file name so it's easier to handle on the local disk, fileserver, webserver or in an email to a customer. But collaborator can't match a file like "OurManual_V1.0.0.pdf" and "OurManual_V2.0.0.pdf" to be the same. Easiest might be to add the option in the webinterface "Upload->File" to select an already existing file and state that this is the newer version of it (although the name has changed slightly) or did I overlook an option in the GUI or the commanline tools?
... View more
Status:
Accepted for Discussion
Submitted on
05-14-2015
06:28 PM
Submitted by
sando821
on
05-14-2015
06:28 PM
I frequently keep one browser (on Windows) open to a review I am creating using the Linux GUI client to upload files to the review. Uploading from subversion workspace might take a number of uploads from various project root directories. I am always dismissing the browser after the launch of each one. It would be nice to have a persistent preferences setting to speficy whether or not to launch a browser after uploading.
... View more
Status:
Accepted for Discussion
Submitted on
04-28-2015
12:30 AM
Submitted by
FSC
on
04-28-2015
12:30 AM
Usually we have a list of SVN revision numbers affected by an issue or change request. To start a review I'd like to copy this list into the Collaborator Client GUI and just go on with the review. But the tool stops creating the review when there is one SVN revision number in the list where only SVN properties where changed. Perfect would be to just continue importing when one SVN revision does not contain any files. (maybe just report the SVN revision numbers without file changes afterwards as a list) I already contacted support and it seems that this is a "feature" so I wrote this new "idea" 🙂
... View more
Status:
Accepted for Discussion
Submitted on
03-31-2015
11:58 PM
Submitted by
marke
on
03-31-2015
11:58 PM
We're reviewing source code in a language that is not currently supported by Collaborator (Ada). It would be useful to be able to add a language syntax highlighting definition. There are other tools, e.g. Ultraedit, that do this with a simple text file that lists keywords against formatting options (colour, bold etc). The filename extensions are then mapped to the language definition.
... View more
Status:
Accepted for Discussion
Submitted on
03-30-2015
06:58 AM
Submitted by
MrDubya
on
03-30-2015
06:58 AM
We would like to be able to use participant custom fields to keep track of process roles for our participants (for example, Jane is the Software Tester and Mark is a Mentor, and Julie is the Auditor). Right now because these fields cannot be set by the person setting up the review, it puts the onus on each participant to log on and change their field. It would be great to allow the person setting up the record to enter this type of participant information which would be more efficient and less error prone than the current workflow supported by Collaborator.
... View more
Status:
Accepted for Discussion
Submitted on
03-25-2015
04:07 PM
Submitted by
Nobody
on
03-25-2015
04:07 PM
It would be nice to run the installer with triggers that could preset the server, username, tray icon, proxy settings and such in a way that would be quick to implement. collabinstaller.exe -url -collab.domain.com:8443 -tray yes -proxy 127.0.0.1 etc...
... View more
Status:
Accepted for Discussion
Submitted on
03-06-2015
11:31 AM
Submitted by
AGuest
on
03-06-2015
11:31 AM
Hello, Would it be possible to find an easy way to let to Reviewer know which files have been updated in a review? Right now the Reviewer must click on the files to see what has changed. Could the "added/changed/deleted" numbers be a difference from the last reviewed/accepted revision as opposed to a running count of all modifications to the file? Even a visual indicator like (*) next to updated files with changes from the previous reviewed/accepted would be sufficient. As things are now, it's a really chore to review code using Code Collaborator. Thanks.
... View more
Status:
Accepted for Discussion
Submitted on
03-03-2015
01:24 PM
Submitted by
Nobody
on
03-03-2015
01:24 PM
Set pages for reviews on the main page so everything isn’t loaded directly when accessing and be able to increase or decrease that review count shown on it.
... View more
Status:
Accepted for Discussion
Submitted on
03-03-2015
01:24 PM
Submitted by
Nobody
on
03-03-2015
01:24 PM
The main portal filter for reviews is pretty basic, we’d like to see increased functionality in this while searching or filtering reviews for each user. a. Time based filters (last updated, created etc.) b. Ability to tag & group set of code reviews (helps when there are multiple code reviews for some big feature) c. Filter based on above mentioned tags
... View more
Status:
Accepted for Discussion
Submitted on
02-27-2015
08:15 AM
Submitted by
CltrAltDelicius
on
02-27-2015
08:15 AM
In a regulated environment the compliance with development processes need to be proved. An organization needs to be able to access all artifacts for about 10-15 years depending on the regulation requirements. Therefore version control systems are used to guarantee the access for all versions of saved elements. If there is the requirement to perform reviews prior to check-in of content, the review data like comments, status and review material must be available during the whole time. But the review material should already be stored in the version control system so that it's storage in the Collaborator cache is only needed as long as the review is not completed. Especially Office documents that are converted to images use a lot of space on disk. It would help a lot to have a button like "Remove uploaded material of completed reviews that are completed since xxx date".
... View more