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.
1285 results found
-
Adding Custom destructive
ANT is unable to change the type on an EmailTemplate from HTML to CUSTOM. To solve that we need to add the EmailTemplate first to the destructive package to have it removed and then add it again with the package.xml
Since this file is not deleted but just changed. It doesn't show up in the deleted items tab.We should add an option to the "Selected Items"/"Changed Items" list to opt-in for adding that to the destructive.
12 votes -
For CI Jobs initiated by Github, dynamically send CI failure / success email to the user who committed to the repo.
Currently, we can only specify a list of users to email, a Slack channel to update, or a Chatter group to post to when a CI job is successful or fails. If there are multiple notifications to a number of people, it's likely they will filter out these messages, so being able to notify the person who the CI Job is most relevant to would be a good improvement.
12 votes -
Allow deployment of PROFILE only
The main reason we considered Gearset was issues with deploying profiles. Half the object settings, if not more, don't come over with change sets. When attempting to use Gearset to ONLY deploy a profile, we had the same issue. So, what's the point of using GS then? When I talked with one of your technical resources he did mention that was not a common use case. I would think it would be for large organizations like ours (over 3500 employees). We may want to spin up a new profile and just deploy that with no app or any other features…
12 votes -
Please add support for decomposeCustomLabelsBeta
Salesforce added the option to configure multiple features in the DX Project Configuration file. One of the is breaking down the big CustomLabels file into individual files where we no longer need to deploy the whole file but just a file (label) that has changes in. Please see SFDX Documentation here - https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm
11 votes -
Create releases in Pipelines not at final stage
Right now you can only create releases at the last environment in a Pipeline. We'd like to have 2 stages so we have a true dry-run of deployment. Our pipeline is
Dev > QA > UAT > Staging > ProductionCreation of the release branch before Staging would allow us to effectively cherry-pick what we want deployed into Staging as we get UAT approvals, do a test deployment where QA does a sanity/smoke test and have greater confidence when we get to our Production release.
11 votes -
Hide re-ordering in a Monitoring job
We have a monitoring job set up to check production changes. However, re-ordering in some components are popping up as false positive. For example, Entitlement Process and Site.com. Everyday I get an email saying # of changes have been made on production. I'd like to not see these false positives in the # so that I do not need to go to each comparison every day just to realize that it's a re-ordering issue.
11 votes -
To add capability to mark (to ignore) not selected items to be able to remember that the particular item is not required to be deployed
When compare source and target, sometimes u do an educated decision to NOT select something, and then selecting the rest of the items. Then if the compare results saved as a Draft Deployment, u may return back to it, and do a refresh for the comparison. In this case Gearset would kindly save all of the selected items. But for items that were not selected by the user, not they are mixed up with the new differences. So user have to remember, that this particular item he did not select intentinally, but this item that is not selected is a…
11 votes -
Allow Package Version Mismatch Bypass for Org Deployments
When deploying a branch to a Salesforce org where there is a managed package version mismatch in the file metadata, it would be nice to be able to bypass this discrepancy as there are occasions where there may be a newer package version in a lower/sandbox org and an older package version in a higher/production org.
11 votes -
Select a set of data deployment templates and run them in order
Ability to build sequence of data load (choose a list of data load templates and have to possibility to run them automatically in sequence). The sequence can be changed.
11 votes -
Ability to specify test suites when deploying apex classes. It would be easier when there are a large # of test classes involved.
Ability to specify test suites when deploying/validating apex classes. It would be easier when there are a large # of test classes involved with a deployment
11 votes -
Use triggering branch as source branch in git-sourced CI jobs
Currently:
We have to define a single fixed source branch in a CI job, when it has a Git-Source.Desired:
Option to say "use triggering branch". It should use the branch, where current commit-hook-call comes from.It should allow Pipelines to test also all development branches e.g. with "Validation only" CI-job.
11 votes -
Support user record migration from production to sandbox or scratch orgs
New users are often created in the production org that need to be monitored and brought back to sandboxes as well. It would be great if the data deployment tool could support moving user records from prod to sandboxes or scratch orgs.
11 votes -
Allow destructive changes from Local File
Allow for the upload of a local file which includes the destructiveChangePost.xml, destructiveChange.xml, and destructiveChangePre.xml files to do destructive changes.
11 votes -
Ability to add custom trigger points to trigger CI from source control
At the moment the tool allows you to only kick off CI jobs when a branch is updated.
This is actually limiting the capability of the tool in itself,
because services like Bitbucket allows you customize trigger points, as to when they should ping the webhook;
such as the creation of pull request, merging a pull request.The two trigger points mentioned above are specifically very important because you would want to run validation CI jobs on the creation of pull request or when the merge completes so that you can actually ascertain if your branch compiles.
Based on an…
11 votes -
Option to validate / deploy only running test classes in deployment set
When deploying, there's a pain point when we want to specify tests to run. It would be nice to have an option to only run test classes that are included in the deployment. Automatically identifying which test classes are in the deployment package should be fairly straight forward:
grep -ri @IsTest ./src/classes
11 votes -
Add "View Validation in Salesforce" to your Github and Teams/Slack Channel messages.
Our pipeline is utilized by some implementation partners that we do not give access to Gearset. They manage their changes that flow through the pipeline with GitHub and receive pipeline updates in a Teams channel. Both of these options have a message to view validation errors in Gearset but the partner teams cannot see Gearset. If these messages included the same "View Validation in Salesforce" option that lives in Gearset, they could be redirected to the Salesforce error page to help their troubleshooting faster.
10 votes -
Show all Github requirements to merge in the Gearset pull request view.
We have required approvals enabled on PRs in Github. Currently when viewing a Pull Request in the Gearset Pipelines view, it does not show that a PR is blocked from being merged because at least one code review approval is needed in Github. This leads to accidentally attempting to "promote" in Gearset and then the Pull Request merge fails. We would like to see these (and any other Github requirements) showing up in Gearset so we are informed which PRs are approved and ready to promote.
10 votes -
extend the GearSet public API to include Data deployments between Sandboxes and Scratch Orgs
Allow triggering Data deployments via the public API to eliminate having to sync data manually. This also includes triggering creation of Scratch Orgs via the Gearset API so that Gearset can instantly recognize them them.
The workflow we would like to automate is: feature branch is checked out which triggers a CI/CD system pipeline to create a corresponding scratch org, do a metadata deployment from a test sandbox, and sync data from the same test sandbox. This allows us to create on-demand full copies of the environment for purposes of E2E testing (inc. external integrations) and feature development that requires…
10 votes -
Option to ignore: <personAccountDefault> in XML
When comparing XML for RecordType permissions in Profiles, some Sandboxes return:
<personAccountDefault>true</personAccountDefault>As part of the XML, even though person accounts are not enabled, this makes comparing annoying.
It would be nice to have an option to ignore this.
10 votes -
Add a Select All that works on filtered items when setting up filters
When setting up the filters, I would like the ability to do a Select All on just the filtered items so that I don't have to manually select each one of them. This would be a huge time saver.
10 votes
- Don't see your idea?