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.
-
Automatic Validation of Pull request for AWS code commit
Gearset does not support PR validation for AWS code commit. We are cloud-native and use AWS extensively, thus missing out on most important feature of gearset. If you can support it it will be amazing and lifesaver for us.
https://gearset.com/blog/set-up-automatic-validations-of-pull-requests/
3 votes -
Clone Comparison from Comparison History
Sometimes, you carefully craft a comparison between source org and VCS only to discover that you have targeted the wrong branch!
It would be nice to go to the Comparison History tab, select your completed comparison and click Clone so you can change the source/target but preserve your selected metadata filters and selections
1 vote -
Add XML tag as optional filter argument to Environment Variables feature
Current Environment Variable feature uses search/replace logic across the entire metadata file. This is a bit "scary". Add optional 3rd argument for the specific XML tab within the file that you want to limit the scope of the search/replace to
1 vote -
New Feature: Filter Custom Fields (and other sub-components) in Comparison Filters
I'd like to be able to exclude certain custom fields from my comparison.
For example we have fields that have environmental differences between orgs that we don't want to deploy. There are also random fields on standard objects that show up as "different" even though they aren't and it would be nice to filter them out.
2 votes -
hide lower upper case differences
One thing that IDEs let you do is mass change your classes to conform variable references to the variable name using proper case
e.g. Integer myFoo;
referenced as myfoo++; // valid as apex is case insensitive
same with [select id from account] which per proper typography should be [SELECT id FROM Account]
since the IDE makes it so easy to do these mass changes; they still appear in the difference viewer as changed lines. It would be nice to extend the current "Hide reorderings" to also do "Hide upper/lower diffs"
This makes scanning through diffs go much faster while encouraging…
1 vote -
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 -
Offer Canadian data residency.
We have clients in Canada that require data residency for data backups/deployments and even metadata deployments/processing.
Please add the option for a Canadian hosted Gearset account.
4 votes -
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 -
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 -
Gearset Scratch Orgs: Generate Passwords
Our team would like an enhancement to how Gearset handles generating scratch orgs from authorized Dev Hubs. We want to be able to provide log-in credentials to non-gearset users in order for them to use these scratch orgs and perform development work.
We want our deployment manager (gearset user) to manage the provisioning of scratch orgs and the retrieval of changes in these orgs to source control. Our developers currently just focus on developing features and are abstracted from the complexities of the deployment process.
To make this process a lot simpler for our deployment managers, it would great to…
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 -
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 -
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 -
Select All Option in Deployment history
It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.
3 votesThis is now possible as long as a filter is applied to the deployment history page.
-
Ability to recreate a reusable list or group for Deployment notifications
Every week we have a larger sized scheduled deployment for logic updates that runs after business hours. There's usually the same 2-6 people (often increasing) that want to receive an email and/or text message when the deployment succeeds. Whoever schedules the deployment has to add each one manually every time, and it would be nice to have a way to send notifications to a predefined list or group of email addresses and/or phone numbers.
It usually has to be the person that schedules the deployment, because if someone goes back to add their own email or phone to an already…
6 votes -
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 -
Allow regex expression in custom metadata filter to be edited
Once you create a regex filter in your your Metadata Filter, you can't select it and edit it. You have to delete and re-enter.
This is especially useful when working with CI job filters
1 vote
- Don't see your idea?