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.
1461 results found
-
More efficient spacing on Pipeline environments
We can only see 4 sandboxes at a time when fully zoomed out. We have 9 sandboxes. Since we aren't able to zoom out further or rearrange the sandboxes we are constantly dragging the screen to pan up and down, to see the state of the orgs.
There is so much whitespace in each node, any chance you could lessen the padding/spacing between the lines in each box/env/node, or between the nodes themselves? Maybe proportional to the max nodes in a single column?1 vote -
1 vote
-
1 vote
-
Comparison of draft deployments
Two teams who are supposed to be working on different parts of the sandbox org have created two draft deployments. I would like to compare these draft deployments to see if there is any overlap of selected items.
1 vote -
Gearset Unit Test Monitoring ignores test methods in classes at V27 or earlier
For older orgs, one may have Apex classes at V27 or earlier. Such classes were allowed to also include testmethods.
Gearset's Monitoring job ignores these test methods leading to a false sense of security that one's org is "correct"
Example class is at V24
class Foo {
void doStuff() {}
static void testmethod myTest() {
new Foo().doStuff();
System.assert(...);
}The myTest will not be run by Gearset Unit Test Monitoring. It will be run by Setup > Apex Test Execution > Foo > Run tests
2 votes -
Help users Deploy Sales Cadences between orgs
Sales Engagement for Salesforce allows users to build Sales Cadences. These seem to be record based, so being able to move these between orgs would be great.
2 votes -
Give CI/CD Users the option to use a shared webhook or a new one in BitBucket
Gearset recently updated its automated webhook setup for new CI/CD jobs to use a shared webhook. For my team, we have configured each webhook for validation jobs to only run on PR creation/update and deployments to only run on branch pushes. By forcing the new jobs to a single shared job, it causes PR merges to trigger validations alongside the deployment (Which is time-consuming and needless).
Also, as my team has many legacy webhooks for our existing jobs, when we add a new job it seems Gearset randomly assigns it to an existing webhook. For our recent deployment-only job, it…
3 votes -
Multiple sort columns for comparison results
It would be helpful to be able to sort comparison results on multiple columns (e.g. first by Metadata type, then by Name). Currently it seems that the results can only be sorted by one column at a time.
1 vote -
Share edit access to a CI job with another user
Currently, only the owner of a CI job is able to edit it. This is a risk, as the owner is not always available to troubleshoot CI issues. It would be helpful to be able to delegate edit access to other team members so that pipelines can be managed collaboratively.
6 votes -
Monitoring dashboard page hangs on loading
Often, if not always, when I first load up the monitoring dashboard it hangs on the loading wheel until I refresh. Doesn't appear to be a problem on any other page.
1 vote -
Attach specific Tests to Feature Branch Manually
I would like to have the ability to force a features jobs to run specific test(s) from the CI screen.
So if GS fails to detect a test class (either by error or b/c its not named in the expected convention) OR would have failed to catch breaking changes elsewhere, we can avoid/prevent this attaching a set of test classes to that feature branches deployment configuration in GS.
3 votes -
Soft delete of deployment History
When a person deletes a deployment history that was successfully deployed, it would be good if that deletion was only a Soft Delete and could be recovered within 90days.
1 vote -
Ability to download/restore data in bulk
We deleted 40 000 records, now we want to download data from the backup for all of them. I can filter them, select for which I want to get it and download, the challenge is, that only 500 records are loaded by default and I can load more in a batch of 500. A lot of clicking to see all of them.
2 votes -
CI job merger conflicts
When resolving CI job merge conflicts, a user has two windows to accept changes from one side of the window. Can we have an option to accept specific components changes from one side and certain changes from the other side.
5 votes -
automatic pipeline deployment on successful validation
For Pipeline jobs, provide an optional feature (ability to toggle on/off) where if an Open PR has successfully validated on the target org, then auto deploy to target org. This is useful when propagating changes in downstream jobs. For example, once code review is done, a PR is merged into DEV by pipeline admin, but it should also automatically be merged and deployed into QA if the validation is successful.
5 votes -
Enforce Promotion Approval Rules
The current UI shows a green checkbox and allows you to attempt to promote changes between environments even if the merge request is unable to be approved. Looks like it in Gitlab there is an 'approved' attribute that may be able to be used.
Alternatively, can have some basic rules but would like it called out its not ready to Promote in the Gearset UI.
4 votes -
Schedule Release Validation
We've run into ROW LOCK issues in the past while running unit tests during validations in production which caused some issues with external Community Users, thus as a best-practice we try to run production validations after business hours.
I'd like to be able to schedule release validations from Gearset, or expose an endpoint that would allow me to trigger a CI validation for a release or PR.
1 vote -
Pipeline Sync Environment & Dev Environment
Currently we only have the ability to sync static pipeline environments. This is well and good but unfortunately syncing the Project branch can be time consuming and confusing Its not as simple as syncing the static environment.
I suggest when I sync the static environment , the sync action automatically opens a back propagation PR to the Dev environment its connected to. Also this sync action should close any pending open PRs against that dev environment that overlap with the sync PR.
3 votes -
Ability to export deployed components for specified period of time
Instead of viewing it by deployment package, it would greatly help us to be able to export all components deployed during a specific period of time. It would help to include the following:
Deployment friendly name
Source
Target
Date and Time
Deployment Status
Owner
Metadata Type
Name
Difference Type4 votes -
Update Deployment Functionality for Education Cloud Standard Picklist
Currently, Education Cloud standard picklist field values are able to be deployed to production. However, the deployment lacks the ability to define active or inactive picklist values. The workaround is to manually activate and deactivate these values after deployment.
This functionality was recently changed on 8/17/2023 for the Academic Session Season and Academic Session Type fields. Requesting the change to be made for all of these fields. Salesforce Education Cloud developer docs (https://developer.salesforce.com/docs/atlas.en-us.edu_cloud_dev_guide.meta/edu_cloud_dev_guide/edu_cloud_intro.htm)
2 votes
- Don't see your idea?