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.
337 results found
-
Enable Gearset login from corporate SSO solution
an additional layer of security and convenience would be to enable Gearset login (that is, login to Gearset) to be done from an enterprise's SSO solution. We use Duo but Okta and others should be supported.
Just like we can login to Salesforce from our enterprise's SSO , we should be able to login to related apps in our suite of enterprise tools via SSO
6 votesWe support SAML Single sign-on in our Deployment Enterprise plan.
-
Add support for the WorkSkillRouting metadata type
WorkSkillRouting is a key object in the configuration of Skills-based Routing for omni-channel (using Attribute Setup, not apex class), please add support for this object to enable comparison and deployment.
6 votes -
6 votes
You can now add your on-prem GitLab instance to Gearset and set up validate pull requests with it. Thanks for your suggestion.
-
Scratch orgs - Create a new scratch org with more than one package
During the creation of a scratch org the system doesn't allow the installation of more than one package...so after create a scratch org we need to install manually the remaining packages.
6 votesYou can now install more than one package when creating a scratch org.
-
CI deployment failure details in webhooks
Webhooks for CI deployment failures simply say "Deployment failed with (179/180 components deployed)" instead of describing the failure in more detail, including the Object and Error Message
6 votesDue to the potential number of items that could be listed we have restricted the number displayed to 12 since there could be hundreds, and provided a direct link to the errors page for convenience so it’s easy to view the full list of errors should there be more.
For the subset displayed, we’ve added:
- Item name
- Type
- Reason for error -
Preserve spacing in formulas!
When deploying components like workflow rules, workflow field updates, and validation rules, it would be great if the spacing (i.e. carriage returns) did not get lost after deployment. This is especially frustrating for complex formulas where care has been taken to properly indent the formula for easy maintenance.
6 votes -
Add org name column to deployment history
We currently have to prefix the deployment friendly name in deployment history with our sandbox/org name to be able to sort by target. It is not easily filtered either as the name column includes both source and target. We would like to have the target org as its own column in deployment history, and have it use the org friendly name as the value if one has been set.
6 votes -
View deployed components from a CI Job
Display components deployed via a CI Job. In my case, there are a greater number of total objects deployed than I would have expected; but, I have no way of viewing the comparison for what is automatically being deployed.
6 votesGearset now supports viewing the underlying comparison that ran as part of your CI job.
Press the `View comparison` button beside a particular entry in the CI history to see the components
-
CI Jobs - Partial Deployments
Allow partial deployments when changes are committed into a branch, so instead of trying to re-deploy the full repo, we should have an option to allow deployment for only the changed items.
6 votesCI jobs can now be set to deploy only certain types of metadata change: new, changed, deleted. If only “changed” is selected, no new metadata or deletions will be pushed by the job, only modifications to metadata that exists in both source and target. This selection is found in the job creation/edit screen. You can also specify whether you want the CI job to respect a package.xml file when deploying from a repository for even finer control over what metadata it deploys.
-
Warn about unsaved changes to my draft deployment
The Draft Deployment feature (https://gearset.com/blog/collaborate-with-draft-deployments-from-gearset) allows me to quickly build up a deployment, but I sometimes press Next to kick off the deployment without saving the current state of things I have selected.
If the deployment fails, I sometimes can't get back and need to go to an earlier version of my draft.
It would be great if you could prompt me to save when leaving the results screen so I don't forget.
6 votesApologies – this feature got pushed back a bit! We’ve now shipped version one, with a couple of small usability tweaks coming soon.
As always, thanks for the suggestion. Let us know if it doesn’t work as expected, either here or in the in-app chat.
-
Add ability to precision deploy custom applications and all other file types
The ability to select specific lines in files for deployments is crucial for org and project management, and should be expanded to all file types. For example it currently is not possible to only deploy a new tab in a custom application, without deploying all other changes in that custom app, which is not manageable with multiple projects/updates being worked on that application concurrently.
5 votesWe've added precision deployments for Custom Applications 🎉
Please get in touch if there's any specific metadata types that you'd like to see in precision deployments.
-
support blank values and/or regex in the "Find What" field on Environment Variables
...support blank values and/or regex in the "Find What" field on Environment Variables.
I would like to replace the value in a field on a Custom Metadata Type with an environment specific value, regardless as to what the value is in the source file. Currently I need to specify an specific value in the source to be replaced.
5 votesYou can now use Regular Expressions with Environment variables.
Simply enter the regex value in the "Find what" field and tick the "Regex" checkbox before hitting "Add environment variable" button.
Thank you for submitting the requests.
-
Option to sort Custom Application XML
While this can be done with VSC custom plugins for SFDX, I think it would be really beneficial if Gearset offered the ability to sort Custom App XML in comparisons in order to see what's actually changing between a source and target for lightning page activations. Due to the way SFDC generates this XML, the way page activations are ordered is very difficult to follow, and I think it's an opportunity to make that easier especially for declarative config users of Salesforce.
5 votes -
Restore/export certain fields on objects
We (the user) would like to be able to restore data, but only select certain fields to be restored.
Usecase:
A business user triggers some automation that modifies a field or specific fields on a large number of records that should not have been modified. In the meantime, other fields may have been modified that were correctly modified. We would want to restore a set of records from a specific backup, but only the specific fields that should not have been modified.5 votesYou can now select which fields you would like to restore, via the "Restore changed fields within <object name>". Example in the attached image.
-
Option to group and show all selected items while creating new custom filters
Option to group and show all selected items while creating new custom filters
5 votesFilters > Selected Only option was release in the custom metadata filter on the 27 Oct 2020
-
Bitbucket pull request add Default Reviewers
When using the "Create Pull Request" link on the deployment screen, please add the "Default Reviewers" to the BitBucket pull request.
Currently we have to edit each pull request and add the reviewers manually.
5 votesThis has been released on October 1st 2021
-
Add a way to "Save" or "Save As" updated filters when in the Refresh Comparison window (like you can in the Compare and Deploy window)
When in the Refresh Comparison window, it seems there's no way to "Save" or "Save As" the updated filters. Looks like you can only access that feature via Manage Custom Filters from the Compare and Deploy screen
Any chance we could get that added? It would be super useful!
5 votesReleased on February 22nd, 2021
-
Add friendly Name to Deployment detail and be able to add/edit from that page
It'd be great to see the "Friendly Name" in the Deployment Summary page.
e.g. https://app.gearset.com/finished?deploymentId=XXXXXXXXX
And to be able to add/edit the Friendly Name on that page, same as it can be done in the Deployment Summary.
Our use case: We audit all our deployments to make sure they have a name. It would be very helpful to be able to send a Deployment Summary link to a user to tell him to add a name if it's missing.
5 votes -
Allow users with owner role to modify and start backups
Allow designated users the ability to modify and start backups without being the owner of the connected org or the person who created the backup.
5 votesYou can now specify other team members to have permissions to manage and start backup jobs they don’t own.
The current owner of the backup job will need to edit the current job settings, go to the new ‘Permissions’ tab and choose the team member and level of access that you’d like to grant them to manage your backup job.
-
Allow users to discard chunks/certain changes before deploying to target
For example I'm on the diff screen and I see my page layout has 5 changes/chunks of changes, but I only want to commit/deploy the first one - please add functionality so that I can discard/ignore the other 4 changes in the file and only deploy the one change I want.
5 votesYou can now exclude fields and other items in page layouts from being deployed using Gearset's new Precision deployments feature: https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
- Don't see your idea?