Help us improve Gearset
We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.
298 results found
-
Add a Select All that works on filtered items when setting up filters
When setting up the filters, I would like the ability to do a Select All on just the filtered items so that I don't have to manually select each one of them. This would be a huge time saver.
10 votes -
Filter Deployment History by Source / Destination
At this time, there does not appear to filter deployment history by specific orgs AND other criteria in the general "filter" text box. I would like to find specific packages deployed to a specific org and also that have a standard friendly name. I am only able to enter text to filter by the friendly name and the additional filters allow for source / destination type, but it does not allow for specific source / destination.
2 votes -
I want to be able to share 'delegate org access' with other team member(s) so they can visually see our security / deployment structure
I want to be able to share 'delegate org access' with other team member(s) so they can visually see our security / deployment structure for reporting.
In this example the fact that "user A owns the connections and has delegated the permission to user B" is not visible to user C. Ideally user C would be able to see that delegation information for auditing purposes.
1 vote -
APEX Class Change
APEX Class Changes Reporting
It would be really cool if, through the monitoring side, if a summary Excel could be created. Excel could have multiple tabs: 1 tab per class change with four columns:
col1 :original line #
col2: original line value
col3: new line #
col4: new line valueHeader could include change DateTime, source/target orgs, Gearset ID, who, etc
Thanks
Ron1 vote -
Allow users to create customized list views on the deployment history tab
It would be immensely helpful for our team, that works across dozens of production orgs and sandboxes, to be able to create deployment history filters (or list views like in Salesforce) that support filtering based on an org's mydomain, the username's domain, or the Gearset user that facilitated the deployment.
1 vote -
Add a deployed components count to the Deployment History table
We'd like the ability to view the number of changes that were deployed from the Deployment History table view so that we can quickly scan the list of recent deployments and identify certain deployments using that additional information.
1 vote -
CI Job Email Notification with PR info
We do receive an email notification when CI job is deployed. Is it possible to know which PR is deployed with that CI Job? Now, the email notification only has the info with branch name, source, target and deployment summary. it'll be great if we can know the PR name that is associated with this CI job, some users, like QA team, will receive emails and know the PR with card info is deployed so they are ready to test. thanks
1 vote -
Add deployment job detail info (such as date/time) at the header in the detail view
I have a markup screenshot for the above feedback but I don't find a way to add attachment here.
1 vote -
Add additional deployed packages
When combining packages for a deployment to a new source, it would be helpful if I could add additional packages to a comparison. There are times when I realize a package or two may have been missed in the original combination, and when reviewing the missing components, I realize a missed another deployed package. Without the ability to add additional packages to the comparison, I must start the combination of packages all over again.
1 vote -
When an Installed Package is installed via GS permission sets with View/Edit All Data system permission don't automatically get updated
When an Installed Package is installed via GS, permission sets with View/Edit All Data system permission don't automatically get updated for the new objects in the package like they do during a manual install. We then have to update the PS via deployment or manually or future deployments will fail with "Read All permission is required for [sObject]". I would think it would be fairly safe to allow GS to automatically add the appropriate object permissions to the perm set in the target org since Salesforce requires that all objects have, at minimum, the same level of access as the…
1 vote -
Export Validated Packages
Ability to Export Validated Packages from Grid, like Deployment History.
1 vote -
Ability for Enterprise User with Role "Owner" to Delete Validated Deployment by Other User
This feature would allow Enterprise user with Role"Owner" to Delete Validated Deployment by Other Users. The reason for doing this is that there could be packages created in error and this would allow release managers who are typically owners to cleanup.
1 vote -
Ability to select source target for Successful Deployment Notifications
Currently successful deployment notifications send every success to the specified addresses. Having the ability to specify the source would eliminate the unnecessary notifications to those addresses. We have a use case in which we only wish to send notifications for successful deployments to our production source.
5 votes -
Mass delete of deployment and validation history
Would like the ability to delete multiple history items at once. The current process of clicking delete and then clicking the confirmation is cumbersome and time consuming when we have multiple users and multiple environments kicking off many CI validations through the day. Failure to clean up the Validation history, especially, eventually brings Gearset CI viewing to a crawl. Having the ability to delete multiple at once and/or a the ability to add a retention period for history would be ideal. Validation history is the most important because you can't filter by time period like you can when you go…
5 votes -
Allow users to share deployment drafts across different Gearset environment
Lets say multiple vendors are working on different environments and done the deployment across all the lower environments using their own Gearset. But coming to the production org. internal team will be performing the deployments using internal Gearset. So Instead of recreating the deployment draft again, it would be very useful internal team can reuse the draft created by vendor in different Gearset environment.
1 vote -
add an account based autonumber field to deployment that could be used as a friendly reference
This could be automatically prefixed to friendly name of the deployment.
Sth like "000035"
Could be a simple counter (that I see you have implemented "This is your NNth deployment...").
If the autonumber would pop up automatically then I would not need to figure out a reference and type it myself.
Currently, info that potentially could be used: datetime (too long) , url (way too long)
2 votes -
Ability to Export SFDC Fields into a CSV File
Would it be possible to get a feature where we can download the fields into a csv file?
1 vote -
Show data hosting option chosen for an account
It would be great to see the chosen data hosting option for an account in the 'My Account' area. Without it security audits will not be able to verify what setting was chosen and will have to rely on documentation held elsewhere.
1 vote -
Limit Connections creation
Currently there is no feature to prevent users in creating their own connections within Gearset.
We need users to follow the permission that was setup on the shared connection. We have only 2 users that have the approval to deploy code from a sandbox to production. As they can set up their own connections then this bypasses our restriction
Having a permission only available to the Enterprise user or a user approved to create connections and delegate access would prevent the bypass of access permissions
3 votes -
Users should be able to specify test classes and save them to draft deployments
Users should be able to specific and save test classes in the comparison stage so they can be saved in draft deployments. Seems like a waste of extra steps to unclick tests and select tests over and over as you work through a deploy.
also when deploys are combined, they would get all the test classes, again, saving lots of time.
8 votes
- Don't see your idea?