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.
1459 results found
-
When the difference between Source and Target, on a particular line, is only in the formatting. Highlight in a different color
From what I can determine you are categorizing the differences as follows:
Code in Source, not in Target – Highlighted in Green
Code in Target not in Source – Highlighted in Red
Difference between code in Source and Target – Highlighted in YellowWhen the difference between Source and Target, on a particular line, is only in the formatting. It would be nice if that was highlighted in a different color than yellow (perhaps grey). It would speed up the review of the code knowing a certain color was only a formatting difference.
13 votes -
Cancel deployment in progress
In Salesforce, you can cancel a deployment in progress: Maybe because a test has failed already and you don't want to bother running the rest, or because you forgot some things.
Can we have a cancel button while a deployment is in progress in Gearset? The metadata api seems to support it:
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_canceldeploy.htm
13 votes -
Allow deployment of Sharing Rules by Rule not by Object
In change sets we can pick individual sharing rules to push (specific ones on an object). However through gearset we can only push the whole object.
13 votes -
Add spell checker to CI/CD pipeline
Spell checker helps maintain a high standard of accuracy, ensuring your content is reviewed in initial PR's itself. Just like how we use Clayton code feedback.
If typos is in customer facing texts in UI (which is can be a big problem in public facing application where large no of users visits.)
It would be good if spell checker can be added as a policy inside Clayton. So that we can find and fix issues easily.
Advantages
* We can also prevent potential PROD P1 errors.
* Enhanced Code Quality
* Improved Deployment Efficiency
* Reduced Technical Debt12 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.
12 votes -
Make Custom Filters a Top-Level Menu Item
Filters are arguably the best part of gearset, especially with the support for RegEx. It is kind of a bummer that they are tucked away in a modal that can only be reached by clicking into a dropdown. Ideally you could just go to Hamburger > Metadata Deployments > Custom Filters and be routed to a dedicated page.
12 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.
12 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.
12 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.
12 votes -
swapping source and target after compare
I was doing compare between our 2 orgs (Source: UAT, Target: DEVSTG) and I realized that I got the order wrong. Should be (Source: DEVSTG, Target: UAT). But the compare has already completed.
I wish there is a way to just flip (swap) the source and target without re-comparing as it takes some time comparing between orgs.
12 votes -
Allow complex filters and child relationships on filters for data loading
Allow complex filters and child relationships on filters for data loading. For example, filter the Account to only load if the Owner is an Active user in the system.
12 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/classes12 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 -
Precision Deployments for Lightning Web Components
It is very much required to have Precision Deployment for LWC components as it is common to have multiple developers working on same LWC
11 votes -
Introduce Import/Export feature for Custom Filters
Expose the underlying JSON/XML for Custom Filters so that we can export it, modify it in a text editor either by hand or with python scripts, then load it back into the custom filter.
For example I have my main CI filter with 50ish metadata types, and every other filter is a subset which I establish by cloning the "master" filter and deselecting metadata types. Whenever I make a change to the master filter I am forced to nuke all the the "detail" filters and recreate them off the master using the above approach.
So many clicks. My preference would…
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 -
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
- Don't see your idea?