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
-
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 -
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
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 -
Export all PDS steps in a package into a excel spreadsheet
Right now , there is no centralized view to look at all PDS steps in a package in one centralized view . If we have an option to export it in an excel document , it’s easy to run through them and complete those steps asap.
1 vote -
Name/Label Environment Variables
I have many similar, but difficult to distinguish, environment variables. When I need to update one of them, I can't easily tell which is which, so I end up having to delete all of the similar environment variables and readd them. It would be nice if we could label the environment variables so I know which ones are which and what environment variable I need to update when the need arises.
1 vote -
Support for decomposed permission sets
Please add support for decomposed permission sets: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_decomposed_md_types.htm. Permission set decomposition makes large permission sets much more manageable. Decomposed permission sets currently fail to deploy through Gearset. I confirmed with Gearset support that it isn't currently supported.
5 votes -
Validate configdata deployments
We are implementing RCA and storing the configdata in source control. Because it is a data deployment and not a metadata deployment, no validations run to ensure the data will deploy correctly. It would be great if there was some way to run validation for the data deployment before merging a pull request that merges it to the org as a check similar to metadata validation.
3 votes -
ACCELQ Gearset integration does not pull out Result URL
Gearset does not show the result link when we trigger ACCELQ tests from Gearset. Error says"Result link has not been sent from AccelQ".
This article details how to access result URL too. https://support.accelq.com/hc/en-us/articles/360029298792-Tracking-status-of-a-test-job-with-external-REST-API. Can you include this info to have a holistic view of test execution
1 vote -
allow a second sandbox to pull PR changes before PR is promoted to main
Currently I have to manually apply a PR from another developer to my sandbox. It would be great if we could sync back a PR before it reached main or sync across from one sandbox to another
2 votes -
Delete feature branch ONLY after production deployment
The ability to delete feature branches only after merging with master branch (which runs the ci job to deploy to Production). Currently the feature branch will delete if there is no PR attached with it. There are instances where I may want to delete a PR to the 'QA' or 'Release' branch but still want to keep the feature branch. Currently this is not possible.
7 votes -
Add The Projects Feature to Modular Pipelines
It would be immensely helpful for my team if gearset implemented the projects feature in normal pipelines into modular pipelines. Testing takes different amount of time and this happens across regions.
1 vote
- Don't see your idea?