Help us improve Gearset
Welcome to the Gearset feedback forum. We love getting feedback from our users on how we can make Gearset even better.
Post your ideas and vote for others – let us know what’s important to you. We’re keen to hear about product improvements, new features, and bug fixes alike. We check this forum regularly and will keep ideas updated with their current status. If you need any further support, please contact us at team@gearset.com.
-
Scratch orgs with packages with InstallationKeys fails to install in CI
When creating a new scratch org you have the option of specifying the package and the installation key. This option is not available in a CI job to scratch org target scenario.
When there are dependencies specified in the sfdx-project.json file that requires an installation key the CI job run fails when the CI tries to install them.
There needs to be a way to specify the installation key, either by a custom JSON field in the sfdx-project.json, or on the CI job itself.
5 votes -
Problem Analyzers don't evaluate changes made from other Problem Analzyers
Even though this example has an easy workaround, it does seem like a scenario which could present issues in other deployments.
In the scenario where a standard application that doesn't exist in the target (ex. Sandboxes and LightningInstrumentation) is included in a deployment (along with its permissions), there's 2 problem analyzers that come into play
"Remove standard application additions/deletions from deployment"
"Remove items which reference the listed components which are not available in the target"
When both metadata types are selected (application and permission) only #1 is flagged. This means Gearset removes the standardApplication, but leaves the references to the…
1 vote -
Retain source control branch selection when cancelling a comparison
If you click "compare now" and then click "cancel" before it finishes, the "compare metadata" screen retains your selection for orgs, but does not retain the branch selection for source control.
It defaults to the first branch by alphabetical order versus what I selected before I cancelled. This can cause confusion for users who do not notice.
1 vote -
Allow standard linux path in sfdx-project.json
if path contains "./force-app" a bug appears, if we write "force-app" it works. so first one should work to
Repro step :
{
"packageDirectories": [{
"path": "./force-app",
"default": true
}],
"namespace": "",
"sfdcLoginUrl": "<a rel="nofollow noreferrer" href="https://test.salesforce.com"">https://test.salesforce.com"</a>,
"sourceApiVersion": "48.0"}
Result :
Comparision failedExpected Result:
Comparision Ok2 votes -
Support for WaveXmd metadata is missing
If we replace default DataSet in Einstein Analytics, it creates another type of metadata "WaveXmd". Support for the deployment of this metadata is missing from Gearset and as per discussion with Gearset team, it's a bug. Could you please fix it.
2 votes -
Don't change the first 2 rows of a metadata file in version control
Usually a Metadata file retrieved from Salesforce starts like this:
<?xml version="1.0" encoding="UTF-8"?>
<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">So two lines, first with the version and encoding UTF-8 and second with the type of metadata.
Now when GearSet does the deployment to version control, either from an Org or a Branch it uses this styling of the first row:
<?xml version="1.0" encoding="utf-8"?><PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
So everything on one line, with the encoding in lower case.
I don't see a logical reason this should be different in the files and is then causing differences in the version control system.
Thanks for…2 votes -
"Next" button on comparison page sometimes does not work
Sometimes, the "Next" button on the comparison page does not work. In the Developer Console I can see a 403 response from "POST https://app.gearset.com/api/static-code-analysis", traced to "raygun.js:2016".
In this case, I have to reload the comparison page.
This happens quite often (I estimate 1 in 5 times).
I don't think that it's a timeout issue (CSRF token or sth.), because just right now I only marked one file in the comparison list and wanted to proceed, and the button didn't work.
On other occasions, I spend a lot more minutes on the comparison page, and the button works perfectly.
…
1 vote -
Keep list of specified tests
When choosing specified tests to do a validation, let's say from a comparison that was created from a bunch of drafts that were combined, the pop-up will show the specified tests that were chosen originally for those drafts that were combined. That is awesome and is exactly what I want.
The problem is the "Fetching test classes from Salesforce" then occurs automatically and replaces that list with the full list of test classes, and check the boxes for all of them, replacing my existing list. That means I have to go back and choose my list of specified tests again.
4 votes -
1 vote
-
Add new connection ends in loop
When I add a new connection via choosing "Salesforce authentication", I need to enter the username. I click on "Authorize". Instead of a redirect to the Salesforce login screen, I see a blank page with a gearset spinner logo. But this screen takes hours and will not redirect. I'm using Firefox and the Org is a sandbox (sandbox is also selected)
1 vote -
For Deleted components, "Changed On" date should be date component was Deleted
After doing a major changes in an org, one can be left with a lot of deleted components to deploy. In the comparison view, they don't show up as expected. The Changed On" date isn't the date deleted. It uses the last modified date in the destination. So deleted something last week could up as last modified 2 years ago.
Ideal: Gearset would to get the Setup Audit Trail via API and display the actual deleted date of deleted components3 votes -
When Field is Deleted Permission Set changes are not recognized for the Field
Let's say we have only one object in the system. Addressc. And we have one Permission Set -> "System Administrator" with only "FieldPermissions" for all fields in the "Addressc" object.
Now I wish to Remove 2 Fields from "FieldPermissions" of the "System Administrator" Permission Set.
1st Field I'm removing just because I do not want the permission to be in the Permission set
2d Field I'm Removing from Permission Set, as I have physically deleted the Field.On Compare And Deploy Page I will See Deleted Field and I will see only one Section to be removed from…
5 votes -
Stop the reordering of XML when deploying to git
At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.
21 votes -
Permission sets not deploying correctly
When deploying a permission set, it was being deployed without the permissions checked, even though Gearset detects that the permission is checked in the metadata compare.
3 votes -
Changed by and Changed Date not populating from DX structure in Repository
Using the DX/source structure in a repository (Github), no "item changed" date is shown for any metadata types in the comparison window.
This leads to gearset not being able to provide last changed date or who last changed anything in a Source DX repository. It's left with "unknown" and makes our comparisons and selections more difficult when users rely on that information.
1 vote -
Summary pages should always include ALL changed files
I believe this to be a bug, but it might be intentional. In any case, the current functionality is, in my opinion, poorly conceived.
If a user adds a deletion to a comparison between an org and git, the deleted metadata is the only item that will show up in Gearset. However, if you inspect the resulting commit in git, you will see that the metadata was deleted along with all of the profiles, layouts, etc that had to be changed as a side effect.
I'm completely fine with Gearset detecting these dependencies and making the changes to them. It…
1 vote -
custom object translation of the Product2 object
The custom object translation of the Product2 object, specifically, is not behaving like the other custom object translations. So when I changed the label of this standard Object : Product2 (Set-up -> rename tabs and labels)
i can't find it in Gearset. I have to make this change manuelly.1 vote -
When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist
When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.
5 votes -
Deployment of pre-valided package doesn't include accurate test counts
We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.
Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?
3 votes -
"Changed on" date on source control side of comparison does not show
We have no way of knowing when the files were last changed on the source control side. Tried only with BitBucket though.
9 votesThat is something we should definitely show. We’ve added it to our investigation list to see if it can be added into the app.
Thanks,
Jason.
- Don't see your idea?