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.
81 results found
-
configure which problem analyzer results to use in CI jobs
Being able to configure which problem analyser results to use in CI jobs.
For instance, we can’t deploy any changes to managed packages because the problem analyser will ignore them (even though we have components from a managed package that we can modify and deploy without issues), that would help to reduce our manual steps during deployments.
46 votesConfiguring which problem analyzers are run as part of a CI job can be done by creating problem analysis templates and applying them to your CI jobs.
For more information on configuring and applying these templates, please see the Gearset documentation here: https://docs.gearset.com/en/articles/4942022-problem-analyzer-templates
Regards,
The Gearset Team
-
Introduce 'ListView' as an option in 'Metadata filter' tab
When navigating to the 'Metadata filter' tab to select filters, there are currently 122 options, however 'List View' is not one of them.
When navigating 'Metadata Types & Components' in Workbench, 'ListView' is described independently, and I have used it previously when deploying via ANT. Therefore I would imagine there is a way to identify List Views independently of 'Custom Objects'.
This would be a huge help with a Production monitoring job, as I do not mind if List Views are updated by certain users in Production, but currently they are flagged as differences. Basically, I want to ignore them…27 votesThis is now released, you will need to update the metadata filter for any jobs set up already to take effect.
You can now exclude list views as well as other subcomponents of custom object.
(Note: named items is not populated for subcomponent metadata types.) -
Cloning package should copy over (prepopulate) description as well as friendly name.
I find myself having to go to the original deployed package to copy the description information or coming up with a new description for the cloned package. Would be nice to have this brought over from the original when cloning a package.
17 votes -
Deploy detected changes to other orgs
Being able to detect and roll back changes to orgs through the change monitoring is cool, but what I'd really like is to deploy detected changes to other orgs.
For example, if we detect a new configuration change to Production, being able to clone that change back down into our Sandboxes directly from the monitoring snapshot would be a real time saver. Or if someone deleted something in Production, being able to make that destructive change down into the Sandbox.
It would help us remove the step of running the comparison and pushing the changes after seeing a monitoring job…
14 votesThis is now shipped and live in the app! We’ve written a small blog post that walks through the feature and the use case.
https://gearset.com/blog/migrating-quick-fixes-in-salesforce-to-source-control
-
Be able to create a CI Job to auto-commit (changes between two orgs) to source control
We have both admins and developers working within our SFDC environments.
Admins typically deploy across environments, so being able to create a CI job to keep the repo updated with these org-to-org changes would be ideal.
12 votesIt is now possible to choose a source control system as the target of a CI job.
For source control best practices, have a look at our whitepaper: https://gearset.com/blog/whitepaper-guide-to-implementing-version-control-for-salesforce
-
Ability to Clone Button on the Draft Deployment page
Can you create a Clone Button on the Draft Deployment page similar to the Clone Button on the Deployment History page? Some times we collaborate on a deployment and one user will take over. We want to be able to deploy the package as the current user, not the original one that made the draft.
10 votesThe ability to clone draft deployments is now available on the enterprise tier.
-
Be able to require a commit message for deployments
Sometimes a user may forget to add in a commit message before deploying, so the history in our source control is "no commit message" which is not editable. Can we add a feature to be able to turn on marking commit messages as a requirement for deploy?
10 votesThis has now been shipped.
The team owner can now enable deployment notes to be required via the setting located in the account summary page.
-
Org metadata snapshots
Allow a snapshot/backup of an org prior to running a deployment. Allow us to use this as a source of a new deployment if we want to revert any changes previously deployed, or at least download the package.
10 votesThis feature is now available. You can take snapshots of your metadata on-demand via the Change Monitoring feature and download the zip file created.
Use the local files option when configuring your comparison.
-
Add schedule deployment for Pipelines
It would be great to add a new feature to cherry pick and schedule deployment for the changes that have reached up till staging/uat and should be released to Prod. Without this feature it becomes difficult to manage releases to avoid downtime.
7 votesYou can now schedule deployment for a release in Pipelines.
-
Allow us to configure a push notification when comparisons are done.
It would be great if we could configure a notification when a comparison completes. Sometimes comparisons take a long time!
7 votes -
Preview Deployment Details in Deployment History
On the Deployment History page, it would be nice to have a little popup window to view some of the files from the Deployment Details instead of having to download the Deployment Report
7 votes -
Allow teams to share custom filters
Allow those filters we can save to be shared amongst our team!
7 votesCustom filters are now automatically shared with other members of the team and can be selected from the saved filter drop down when setting up a comparison.
Blog post on usage: https://gearset.com/blog/shared-team-comparison-filters
-
Allow me to configure my default landing page on logging in
Specifically, I use the Pipelines most of the time and would love for that to be there as soon as I login. While my use case is Pipelines specific, I would guess that others might want a different page when they login, so it would be nice to be able to configure this on a per-account basis.
6 votesWe've recently made a change to let you select your default landing page in your account settings.
-
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.
6 votesHi there,
We have now added Canada as a data storage location. You can head over to app.gearset.com - click on create new account and sign up for the same.
Thanks
Gearset team.
-
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.
-
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.
-
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.
-
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.
-
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
- Don't see your idea?