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.
1493 results found
-
Manual Deployments/Validations should allow Webhooks to allow notifications
Would like the ability to specify a webhook to send notifications when a manual validation or deployment is done outside the pipeline. We have more users interested than we have gearset licences.
1 vote -
Improve Monitoring Job filtering and alerting
My team and I find specific alerts more actionable than broad alerts. Right now, that means I need to create unique Monitoring jobs for the same environment and use the metadata filter to narrow down what each job focuses/alerts on. I wonder if there is a more scalable/efficient solution where I can take a single snapshot of an org but configure multiple alerts based on rules that filter specific details from the single snapshot.
To take filtering one step further, we'd love the ability to filter based on the actual returned data in the snapshot. For example, I may want…1 vote -
Email-based Pipeline Notifications
The new Pipeline Notifications feature only supports Slack and Microsoft Teams notifications while other notification locations within Gearset support email. We would love to use Pipeline Notifications but cannot because we don't have access to integrate with the supported options. It's confusing that some notifications on the platform support email while others don't.
1 vote -
Support a .gearsetignore file to exclude non-metadata paths from CI triggers
Salesforce DX repositories hold more than deployable metadata: AI agent guidelines, documentation, package.json, .prettierrc, lint configs, scripts and so on. A push that only touches these files still starts a CI job. The job deploys or validates zero components, and on a production pipeline it can still run the full test suite, which can take an hour or more.
Gearset has no way to exclude paths from this. .gitignore isn’t a fix because it stops the files from being tracked at all, and we need them in version control.
Proposal
A .gearsetignore file in the repository root, with the same…3 votes -
Enable getting updates to developer environments from an integration branch rather than only from our base branch (main)
We'd like a pipeline setting option to specify a branch that updates to developer sandboxes come from, rather than being locked into using our base branch, which is main. We often have features sitting in our integration branch for up to a month before they work there way to main/production. Sometimes we take on new stories that have dependencies on another story that is not yet in main, but only in our integration branch/environment. We'd like to be able to specify a branch that updates to developer sandboxes come from so that we can use our integration branch instead of…
2 votes -
Audible/Visual Notification when Cam is ready
The ask: an audible 'pop' sound (like the Support chat reply 'pop' or a push notification to my desktop) when Cam is done processing
There are many times when I fire up a conversation in Org Intelligence or Agent and navigate away while I wait for it to cook. This would help me get back to focusing on the project, while still feeling okay to jump over to answer a quick email/Slack while I wait.
1 vote -
Org Intelligence Scroll
This is so silly, but when I went to Org Intelligence, I scrolled down on the page itself and could not figure out where the rest of my orgs were listed. Turns out you have to scroll within the list of orgs... I feel like a slight change in the UI to show a mini-scrollbar or something would've helped me here. Thank you! :)
1 vote -
Wrong deletion date for related record in the backups
Wrong deletion date for related record in the backups: due to full backup being done only once a week when we delete for example Opportunity, we can see only exact deletion date for it but even though it's related records are deleted at same moment, in the backups it's reflected only after full backup run.
1 vote -
Support reusable metadata filters for Monitoring jobs
Gearset provides the ability to reuse metadata filters across CI jobs which allows you to configure it once and have the changes apply to all jobs referencing it. https://docs.gearset.com/en/articles/618760-manage-custom-filters-in-ci-jobs
The same functionality is missing for Monitoring jobs. It would be very helpful if Gearset adds this feature for all existing and future locations where metadata filters are configured for a job.
1 vote -
Expose all Gearset operations through APIs
Gearset can only be configured by a human through the UI. This leads to long, manual, and error prone setups with no way to create reproducible automation for common scenarios. We'd greatly benefit from having the ability to automate these setups through APIs or some Infrastructure as Code framework. Here are some examples of operations I'd love to automate or integrate into other workflows: initiate CI job PR validations, clear existing Updates from a developer sandbox, manage org connections, manage developer sandboxes in a pipeline, manage user permissions, manage monitoring jobs, manage unit testing jobs, mark manual steps as completed,…
2 votes -
Removing a dev sandbox from a group loses downstream environment connection
When you remove a developer sandbox from a developer sandbox group, Gearset "loses" its previous downstream environment connection. You need to edit the pipeline to reattach it to the environment to recreate the intended flow.
The sandbox groups should just be for organizational purposes, and that management shouldn't impact the actual pipeline connectivity for the sandbox. It's currently very easy to miss the lost connection which leads to a desync'd sandbox that's now missing out on sandbox Updates and manual deployment steps.1 vote -
Provide an easier way to cycle through all changes in a comparison
Gearset currently has arrows to cycle through the next and previous changes within a single metadata row. When you click the next arrow on the last change, it cycles back to the first change within that metadata.
I'd prefer the option for the next arrow to move you to the first change of the next metadata row instead of looping back to the top of the existing one. This is how Azure DevOps PRs works and it greatly speeds up the process when reviewing a large number of changes across multiple different metadata entries.1 vote -
Show manual steps in line with Developer sandbox Updates
Right now, the Updates UI shows all the pre/post deployment steps to the right of the individual commits while selecting what to back-promote to a Developer sandbox. We often have scenarios where a future commit will fail because a previous commit has a post deployment step that needs to be executed first. This causes the Admin to have to cancel the Updates and manual click through the commits to figure out how to break up the Updates based on the steps. I suggest that Gearset intermingles the pre/post deployment steps with the commits to more easily show where those steps…
1 vote -
Developer sandbox Updates seeding for Long-Term Projects
The Updates feature of developer sandboxes is very useful to keep our sandboxes up to date with changes flowing through our pipeline. We are running into an issue though when using it within a Long-Term Project. We've faced scenarios where we need to either refresh or create a new sandbox and integrate it as a dev sandbox feeding into the Long-Term Project's final static org. We have no easy way to catch that dev sandbox up to the current state of the static org because the metadata promoted there hasn't been released to Production yet.
It would be very helpful…1 vote -
Missing environments while configuring pre/post deployment steps
While creating a pre/post deployment step, you have the option to select specific environments. That list does not contain all the connected environments within our pipeline. It seems to only show environments that are along a direct downstream path of the step's source.
With all of Gearset's automation and back-propagation functionality, it is possible for that PR/step to arrive at an environment that isn't along a direct downstream path of the step's source. Because of that, I would expect to be able to account for all environments in a pipeline while creating a deployment step. We often have steps that…1 vote -
Improve available outgoing webhook variables in CI jobs
Gearset continues to add information to the deployment history UI of CI jobs. Some helpful recent additions were more context around the PR that triggered the deployment, like the PR number and branch name. Those details weren't exposed through the outgoing webhook variables available in CI jobs though. https://docs.gearset.com/en/articles/2652073-outgoing-webhooks-in-continuous-integration-jobs
It would greatly help our automation efforts and external integrations if the outgoing webhook variables are maintained and at least match the details provided on the UI. Most of the existing variables are limited to the context of the CI job itself, so anything that exposes more details about the source…
1 vote -
Problem Analyzer Previews
I often find Problem Analyzer descriptions difficult to understand. It would be extremely helpful if Gearset included an example of the "before" and "after" within each Problem Analyzer's expanded section.
I think the idea could be taken one step further by showing a subsequent "comparison" view which allows you to easily review the total impact that all of the selected Problem Analyzers will have on your commit.1 vote -
Audible Notification when Pipeline Updates have Deployed
The ask: an audible 'pop' sound (like the Support chat reply 'pop') when Pipeline updates are done processing
We have dev sandboxes, a Full sandbox, and production as our 3 layers to our Pipeline. When my personal dev sandbox gets really behind on updates, I hit errors when running ALL updates, so I do ~10 updates at a time. I fire up one wave of updates and navigate away from Gearset.
If I remember to come back to Pipeline in a timely fashion, it almost always is still processing. Or I often forget to come back to fire up a…
3 votes -
Audible Notification when Pipeline Updates have Deployed
We have dev sandboxes, a Full sandbox, and production as our 3 layers to our Pipeline. When my personal dev sandbox gets really behind on updates, I hit errors when running ALL updates, so I do ~10 updates at a time. I fire up one wave of updates and navigate away from Gearset.
If I remember to come back to Pipeline in a timely fashion, it almost always is still processing. Or I often forget to come back to fire up a second wave of updates.
If I had an audible 'pop' sound (like the Support chat reply 'pop') when…
1 vote -
Ability to create release with 0 PR
Creating an empty release with no PRs, which deploys at the scheduled time (or does nothing if it's empty).
Currently I can not create an empty release. Gearset does not allow me to create empty release. If I select a PR then only it gives me an option to create a release if no release is created or add to release if a release is already there.
My request is if I can just create empty release without PRs that would be amazing.
Note: We are in the process of making our deployment process fully automated and this is the…
1 vote
- Don't see your idea?