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.
210 results found
-
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 -
Allow pre- and post-deployment steps for items that cannot be deployed through the Metadata API
We encounter a variety of user stories that require manual changes to items that cannot be deployed through the Metadata API. If these are the only changes required, there is no way to track these pre- and post-deployment steps, since a PR (and thus a metadata commit) is required to add the steps in Gearset.
3 votes -
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 -
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 -
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 ruin my day when a flow activation fails - Add Flow Activation Fails in Summary
The summary only shows the flows that were successfully activated. It doesn’t surface activation failures for individual flows.
So the behavior you saw can happen:
The deployment completes successfully
Gearset attempts to activate all flows after deployment
The summary lists only the flows that activated
Any flow that didn’t activate won’t appear as a failure in that summary
That’s why it can look like a “clean” deployment even if one flow stayed inactive.1 vote -
Restrict the branch from the promotion if developer add any metadata type other then the metadata types on CI Job filter.
Currently Gearset is giving a warning on PR if metadata type added on the branch doesn't present in CI Job filter, instead if we a have something to restrict /block promotion it helps.
Scenario: Even if developer uses CI Job filter at time of comparison still, they will be able to compare additional metadata types, hence they commit those to the branch. At the PR level it is showing as warning message which developers are missing and promoting changes. After promoting they are coming back and asking why those haven't deployed even it is showing as deployment successful.
1 vote -
Pipeline: a more selective developer sandbox alignment
In the pipeline, let's say there are more developer sandboxes and a feature-branch is created from one of them and merged until the main branch.
At this point, only the other developer sandboxes must be aligned from main, there's no need to align the one where the feature-branch was created from.
Therefore, the pipeline should show the symbol 'need of alignment' only on the other sandboxes.1 vote -
Auto merge of PRs
Once the validation process is successfully completed for the respective PR, it would be very helpful to have an option for automatic merge and deployment. This would streamline the release process and reduce manual steps.
Additionally, it would be great if we could have control at the org level to enable or disable auto merge functionality. This way, teams can decide whether they want to use auto merge based on their workflow preferences or organizational policies.
Thank you for considering these enhancements!
10 votes -
Auto-cancel the old CI/CD process on new commit pushes.
When a validation is runnnig based on PR changes, it would be great to cancel old validation job on gearset, as well as the validation on the salesforce on new commit pushes. That way, redundant jobs are not stacking to be validated and increase the CI/CD flow when multiple PRs are there
2 votes -
External Client App
I have been testing out the ability to promote External Client Apps through a pipeline. I found that if I include the 5 files (.eca, .ecaGlblOauth, .ecaOauthPlcy, .ecaOauth, and .ecaPlcy) that define the ECA, I receive an error of 'We couldn't update your OAuth Link...'.
But, if I edit the .ecaOauth file and remove the oauthLink tag/value then the promotion succeeds. This is an optional tag is set from the source org, and can be removed before promoting. It would be great if this was handled automatically, maybe with the problem analysis tool.
1 vote -
Strategies to Maximize CRM Efficiency in Large Enterprises
Large enterprises often face challenges in managing vast amounts of customer data while ensuring seamless communication across departments. To maximize CRM efficiency, organizations should focus on process standardization, automation, and integration of multiple systems. Implementing clear data governance policies ensures accurate and consistent information across teams. Leveraging advanced analytics helps identify trends, forecast customer needs, and improve decision-making. Additionally, investing in employee training ensures teams fully utilize CRM capabilities. Collaborating with top Salesforce consulting companies can provide specialized expertise to customize and optimize CRM systems for complex enterprise requirements. Regularly reviewing workflows, updating tools, and staying informed about emerging technologies…
1 vote -
There should be character limits from 0-2000 for environment variable as we need to store certificate.
These are some credentials that should be stored into gearset as namedCredentials and customSettings make it more work around so It will be good if we can configure some things in Gearset as it will be more efficient in term of implement and will reduce the human errors.
1 vote -
Can deployment bundles be created automatically based on JIRA labels or fields?
Can deployment bundles be created automatically based on JIRA labels or fields?
1 vote -
Change the test running options in pipelines
The options for tests in CI jobs/pipelines don't seem to offer quite what I need for sandbox deployments. Specifically, I want to be able to run all the tests when class/flow/trigger metadata is changing but no tests when tests metadata do not change.
This is possible to do when deploying to production orgs by using the "Salesforce default tests" option (see https://docs.gearset.com/en/articles/1376067-setting-apex-test-levels). But it is not possible in sandboxes.
In sandboxes, the "Salesforce default tests" option runs no tests at all which I don't want. I also don't want to run "All your tests" because if merging a branch…
1 vote -
checkbox
When viewing Open Pull Requests in an environment in a pipeline, the user can click the checkbox beside the pull request thinking they have selected that pull request. Clicking the checkbox does not currently select that Pull Request in the UI. It would be nice if clicking the checkbox would also select the current Pull Request in case another function such as "Close pull request" (trashcan icon on right pane) is being selected.
It is easy to think you have selected the pull request when clicking the checkbox for it and in turn close the wrong pull request as a…
1 vote -
Add a link to open the deployment when a change is being promoted
The pipeline view only shows that a deployment is "running" after promoting a change. It would be useful to have a link to the deployment job and be able to view the deployment status in gearset.
1 vote -
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
- Don't see your idea?