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.
1417 results found
-
Make pre/post deployment steps conditional on developer sandboxes.
Pre/Post deployment notes can be set to pertains to various static environments but they always apply to sandboxes after a back deploy. This should be conditional-- most of the time I only set them applicable to prod and they aren't applicable to developer sandboxes.
5 votes -
Grouping more than five sandboxes should not hide them
When grouping sandboxes, having more than 5 in a single group adds a scrollbar, and hides any additional sandboxes added to the group. This decreases visibility into sandbox status. I missed that there were several sandboxes that were very out of date simply because I couldn't see them on the pipeline. All sandboxes on the pipeline should be visible for visibility.
1 vote -
Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to m
Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to mask our homeowner records in Account and Contact. We do not want to mask our dealer records. If we could limit the records that are being masked by using record types, this would enable us to use your solution. Thanks!
1 vote -
Put a "Simplify Differences" toggle at the entire comparison level instead of each item
Add the "Simplify differences" toggle to be enabled at the entire comparison level so you can filter out items that don't have any actual changes besides metadata being moved around within the xml file by the salesforce API. This way, if there are items that don't have any true differences, they can be quickly filtered out at the comparison level instead of drilling into each one and having to "simplify differences".
This would help especially with custom objects, where the salesforce api moves the Action Overrides around causing the analyzer to flag objects as different between orgs, when in reality…
2 votes -
Add an integration for Google Chat that includes an integration for Change Monitoring and Unit Testing.
Recently, it seems that Google Chat has reached some feature parity with Slack in that it has a defined integration avenue for adding notifications to Google Chat. I have found that I can set up a custom webhook to Google Chat for the CI jobs, but webhooks are not available on the other 2 features I am looking for notifications from.
I would either like to have:
a.) An integration for Google Chat with an app on the Google Chat side that we would add for the connection to our Gearset
b.) Webhook availability for more notifications, so I can…2 votes -
Feature Request: Deployment Blocking Based on Daily Unit Test Job Status
Currently, Gearset lacks a feature to block deployment CI jobs to the respective environments when the associated daily unit test job fails. Implementing this feature would be advantageous in ensuring that appropriate testing quality gates are established to prevent changes from being deployed in the event of test failures. This enhancement would significantly improve our deployment integrity and testing processes.
4 votes -
Pipeline Notification for Metadata filter for Missing components
If I am committing some code via pipeline, in my feature branch that includes a metadata not present in my current CI Job filter, Can I get notified from Gearset that commited/merged metadata not present in the CI Job Filter?
1 vote -
Ability to "Hide" Sandbox Groups on Pipeline Page
In the Pipelines page, it would be very helpful if we had the ability to "hide" entire sandbox groups from view. This would make it much easier to quickly find and focus on the environments that are relevant to the logged-in user.
Ideally, this "hidden group" setting would persist across logins and page refreshes, similar to how the "collapse group" feature currently works.
I'm sure an "unhide groups" feature will be needed with this as well, in case a previously hidden group becomes relevant again.
1 vote -
Allow Archive Notifications for both successful and failed runs
Currently, when an archiving policy runs, you can send out a notification if a run has been successful or a notification when a run has failed. I cannot see a way to have both notification types as I would like to see at a glance how many records have been archived in each run, but I also need to know when it fails with permission issues after deployments or major releases. I do not go into the Archive section every day.
1 vote -
add support for lightning types (LightningTypeBundle)
Add support for lightning types (LightningTypeBundle)
1 vote -
Adaption of Deployment frequency of CI jobs
While setting up a CI job, I recognized there are only automatization options up to every 24 hours, which is once a day. Currently there is no possibility to deploy e.g. every second day or even more important to us, every week/ every second week. Please add this possibility when adding CI jobs, to have a slower Deployment cycle to e.g. demo sandboxes, that don't need daily deployment.
2 votes -
Display the developer who opened the PR throughout the entire pipeline flow.
As a Release Manager, I have difficulties identifying the developer responsible for the PR.
The developer's name only appears when they open the PR at the beginning of the process, and in the following stages, it shows the system user's name from git that Gearset uses to open the PRs up to production.
Since I need to easily know who opened the PR during the release creation, I have to open the feature card to find the developer. ...
1 vote -
Enable multiple orgs to act as build agents for single pipeline step
Occasionally our queue is backed up waiting for dozens of PR's to validate, this happens because a single org can only validate one PR at a time. It would be helpful for a solution that allows us to attach multiple orgs (sandboxes or scratch orgs) to a pipeline step such that multiple PR's could be validated in parallel. Then when a PR is deployed it could easily be deployed to all of the attached orgs.
1 vote -
Solution for enabling parallel builds validations, i.e. multiple build agents
Occasionally we have a backup in our queue PR validations where dozens of tickets all have to individually wait for there spot in line to validate. It would be great if we could spin up multiple orgs (sandboxes or scratch orgs) and attach them to a single pipeline element such that each org could help load-level the validation queue.
1 vote -
Preserve Precision Selections through Fetching the Latest
You're precision selections feature is absolutely amazing! Every time I use your tool it just gets better and better and this feature has me hooked. It's been huge with lightning web pages which often have multiple changes in UAT and need to be separated for deployment.
We prep deployments before sending to UAT. Occassionally, there has been a big delay since the package was originally validated. If I need to go back to the original draft deployment and refresh the selected items to ensure I'm not overwriting something else that went out, the precision selections are cleared.
- There is a…
1 vote -
Customizable Metadata Deployment Order - Destructive change and reference changes
We should be able to define the order of metadata deployments. For example, when deleting a custom field and updating its references, we currently need two separate deployments: one for modifying references and another for field deletion. Allowing us to set the deployment order—modified references first, then field deletion—would enable this in a single deployment, streamlining the process.
2 votes -
Deployment Failures in Pipeline
The flow of a pipeline promotion is as such:
- Validate deployment to org
- (on success) Merge PR into base branch AND move PR to "Recent Promotion History" tab
- Deploy to org
IF the deployment fails at that point, or is partially successful it would be great to denote that somewhere within the CI job within the pipeline. This would give the devs.admins more visibility into the true state of their features. Maybe we don't even move to the next environment until after a successful deployment.
1 vote -
Dependency-Aware Deployment Sequencing in Gearset
Currently, deployments in Gearset can fail when interdependent metadata components are deployed simultaneously without respecting their dependencies. For example, deploying a new Lightning page that references a report or dashboard will fail if both are included in the same deployment, as the referenced report or dashboard does not yet exist in the target org.
While the current workaround is to manually split deployments into separate feature branches based on dependencies, a more intuitive approach would be for Gearset to detect these dependencies automatically when multiple related components are included in a deployment. The tool could then offer options to handle…
4 votes -
Automatically Backfill Dev Environments with Pull Request When Changes Are Promoted Downstream
Description:
Currently, Gearset’s pipeline tool does a great job of back-propagating changes between static environments when a change is made further down the pipeline. However, this behavior does not extend to developer environments, even if the change originated from a feature branch tied to that dev environment.Problem:
If a developer starts work on a branch in their dev environment, and then that branch is promoted down the pipeline (e.g., through UAT, Staging, etc.), and changes are made to the branch further down (e.g., hotfixes, last-minute edits), those updates do not automatically get proposed back to the original dev environment.…
1 vote -
Add Monday.com as a source for User Stories
Add Monday.com as a source for user story integration
1 vote
- Don't see your idea?