Status:
Selected for Development
Submitted on
09-14-2022
08:15 PM
Submitted by
it_scm_technolo
on
09-14-2022
08:15 PM
We need to restrict all users from creating new projects in collaborator web application because it should allowed only for system administrator.
... View more
See more ideas labeled with:
I am using Collaborator Enterprise 13.6 and trying to archive my nearly 1 TB of data in my Content Cache folder on my server. We have tried to archive off to a separate network location (to free up space on my server) and it will not copy the files. We have to do this the brute force method and archive to a location on the same server (small increments) then copy that archive to the other network location. We will have to do this with each incremental archive. Then they are not together, but they are still individual archives. I would like to request that the ability to archive to another network location be added so that when an archive is done, the data is all together in one Content Cache folder, and I don't have to look through a bunch of separate archives to find the review I want to restore.
... View more
See more ideas labeled with:
0
Kudos
Status:
Implemented
Submitted on
08-15-2022
07:49 AM
Submitted by
jonathonchurch
on
08-15-2022
07:49 AM
In a large review with many files and multiple participants, if you are not the first or last participant, it is hard to know which column is yours in the list. This makes it difficult to see if you have already accepted a review which causes unnecessary scrolling. A few possible solutions: Always make the logged in participant the first column of the list of participants. May not work well when someone how isn't an participant of the review is looking at the review, but this is rare and they probably aren't looking to see what files they haven't reviewed. Draw the left and right column lines with a heavier weight. For example:
... View more
See more ideas labeled with:
0
Kudos
Status:
Implemented
Submitted on
07-13-2022
06:58 AM
Submitted by
IanStroud
on
07-13-2022
06:58 AM
see https://community.smartbear.com/t5/Collaborator-Questions/Collaborator-13-12-131200-miss-draws-text-panes-on-Firefox/m-p/236254/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEw1Sk0wSjU1NVZIUk1afDIzNjI1NHxTVUJTQ1JJUFRJT05TfGhL#M2825 Suggestions: 1. Properly test your systems with all supported browsers. 2. Monitor the community questions and step in when a bug is reported OR 3. Provide a proper bug reporting mechanism so the issues can be raised by users.
... View more
as it is now, home screen fields that are added and ordered will reset to default. The ability to have these personal preferences retained would be great.
... View more
See more ideas labeled with:
Rather than having to click on each file to exclude it would be good if we could exclude content by folder, by file filter, by holding down the shift key and selecting 15 files at once. Things that allow working with and excluding large lists of files easier and less time consuming to ensure just the essential files are included in any review. Not much thought or effort has been put into the current mechanism.
... View more
See more ideas labeled with:
currently the ability to re-open reviews is based upon the review templates. It would be better to have this setting be at (or included in) the limited admin level. It is not typically a setting we desire everyone to have, but having a limited team (quality) be able to re-open is highly desirable.
... View more
See more ideas labeled with:
0
Kudos
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.
... View more
See more ideas labeled with:
when custom fields are added to checklist, the selection of the custom fields should auto select the checklist item and record the user/date time stamp the same as happens with a checklist item (default) when the left button is activated. custom fields in this area usually would be a yes,no, n/a override of a simple button toggle provided by default. additionally, having 2 custom fields (yes/no and notes) it would be great if you could mandate a note is entered for no, but not required for yes.
... View more
0
Kudos
It would be great if this setting in the roles area could include a selection of 'all the participants with this role' we have a role that is required. However sometimes we need to have 2 (or more) people with this role participate. There is no way to configure the tool to say everyone on the review with this role needs to participate.
... View more
See more ideas labeled with:
We have several projects where funding is volatile, and work efforts get shut off/turned on with very little notice. Collaborator reviews stay open indefinitely, which is not ideal. Users also don't like pages of stagnant reviews on their dashboards. We would like to move these reviews to a deferred state, rather than have to cancel them, since they may resume again in the future. It makes sense, and would be a useful feature.
... View more
We would like to know if Collaborator integration with the DOORS Next Gen requirement manegement tool exists or will be implemented.
... View more
Status:
Postponed
Submitted on
03-07-2022
01:34 AM
Submitted by
puneetkanchi08
on
03-07-2022
01:34 AM
Hi, Would love to have the capability to order the the fields of the Review in the Review page. For example - I have a Review custom field that needs to come right after the 'Deadline' field. So the capability to move change the order of the fields would be helpful. Thanks, Puneet.
... View more
See more ideas labeled with:
1) Defects: List all defects associated with all the reviews in a project 2) Reports: Add a report to list all reviews for a project
... View more
Status:
Accepted for Discussion
Submitted on
02-08-2022
06:46 AM
Submitted by
nickf
on
02-08-2022
06:46 AM
I would like to see support for reviewing local HTML documents, where I can navigate, drop pins and see differences from within the Collaborator environment. Something related has already been done with the Simulink review tool.
... View more
See more ideas labeled with:
I would like to suggest that removing of names can't happen without a confirmation. This is especially true when the removal of the name will allow the review to be completed prematurely. If there was a confirmation screen that popped up that said "Are you sure you want to delete this person even if the review will complete at this time, and in order to re-open the review you will need the assistance of an admin?" We have had several recent examples where a participant was removed from the review before the replacement participant was added, and the review ended prematurely and had to be re-opened by an admin. The proper sequence would be to add the new participant before you delete the old participant. The review would not end in this sequence because the new participant would have to approve of the review before it completed. People do not know that they need to add before they delete. The confirmation screen would not prevent this from happening in all cases, but it is better than not knowing that they will cause problems if they delete first. We are open to other suggestions, if someone has a better way of avoiding the situation.
... View more
Status:
New Idea
Submitted on
01-19-2022
08:33 AM
Submitted by
johnmcdraper
on
01-19-2022
08:33 AM
Bringing back an old thread - I'd like anyone with Admin privileges to be able to move a review to Completed. We've had several instances where someone has left the company, or is on extended leave, and their roles is required to move a review to completed. On solution is to shuffle roles - while that will allow a review to close, it's "not right". If the author of a document is out sick - yes I can assign the author role to someone else - but now you are fudging the review records in order to get the closure. Later when an auditor comes in we have to give a song and dance as to why the roles in the review don't represent the actual roles the staff members have. We shouldn't need to alter the records to move things forward. The review is more than a record of defects - it's a record of who did what, and we shouldn't need to compromise that to get around a technical glitch.
... View more
See more ideas labeled with:
Status:
Deferred to Support
Submitted on
01-03-2022
08:34 AM
Submitted by
Taki1999
on
01-03-2022
08:34 AM
Several of our users complain about the volume of emails that they receive from Collaborator even when the setting is adjusted to minimal. Is it possible to collect the notifications in a different format such as a single digest email instead of an email per review? (e.g. You are a participant in X reviews which are past due. You have Y stalled reviews currently.)
... View more
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 not https:/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 email
... View more
See more ideas labeled with:
Howdy, Please add Code Collaborator support for AWS Code Commit repository integrations to the web client. Example of this current functionality can be found here: https://support.smartbear.com/collaborator/docs/source-control/git.html https://support.smartbear.com/collaborator/docs/source-control/repo-hosting/index.html In the same way that Github, Bitbucket, and Azure can easily be integrated to the Collaborator, I would like for this process to also function with AWS Code Commit Repos. I may currently use Code Collab and AWS Code Commit via the client gui and local changes, but I would also like to have direct repo integration like the hosted repos do. Thanks.
... View more
See more ideas labeled with: