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.
51 results found
-
scroll bars
Get rid of the scroll bars in the open pull requests tab caused by the queue section overflowing its bounds.
Also, allow us to post screenshots here. :\
1 vote -
Prevent Pipeline Paths from crossing Static or Developer environments
Sometimes depending on how you setup the pipeline you can end up with pipeline paths crossing/going under static environments and developer sandboxes.
This gives the impression that they are connected when they are not.
I would like it to look like this: https://drive.google.com/file/d/1s59BS47wEuHFA8Grb0SLdFSH00AgWw0W/view?usp=sharing
But it ends up looking like this: https://drive.google.com/file/d/1BLFrHd0HTR9LTLSoUw_34BqAWgvDa1SO/view?usp=sharing
1 vote -
Fix comparison default date range
- Click new compare and deploy
- Select a source and target.
- Notice the date range says "Today" but DON'T change it.
- Click Compare
- Notice the date range now says "All Time"
Repeat...
1. Click new compare and deploy
2. Select a source and target.
3. Notice the date range says "Today"
4. Change the date range to anything else
5. Change the date range back to "Today"
6. Click Compare
7. Notice the date range now says "Today"1 vote -
Fix pre/post deployment steps from disappearing.
- Add Pre or Post deployment step
- Click "Specific environments only"
- Click the "x" to remove all the environments Notice, the entire "Environments to run against" section disappears To get it back you have to cancel, and do it again.
1 vote -
Removing an Updates Sandbox from the pipeline should close all associated PRs and branches
I noticed that deleting a sandbox with outstanding updates from the pipeline does not close any associated PRs. These and their branches should be removed from source control automatically. The branches are especially problematic as the GUIDs make it extremely difficult to associate them to an environment and determine if they are no longer needed.
1 vote -
Deploy the Name of object without truncating
Hello,
I deploy from Sandbox to Prod.
I have a custom object where the Name is 42 characters long on the Sandbox.
When I deploy, it has only 40 characters on Prod.
If I run compare, 42 on sandbox, 40 on Prod.
If I deploy again, still 40 on Prod.
I can of course change the Name by hand on Prod to 42 characters.
Thanks
Stephane1 vote -
Team members are able to create release with no access to CI job
Team members are able to create release with no access to CI job.
"Promote changes" is gray as expected, however "Create release" works which is awkward1 vote -
Gitlab Self Managed Issues
We suspect that reading the 'weburl' response field for the specified branch from an API call to GET 'v4/projects/$projectid/repository/branches' might be causing a problem when using public Gitlab proxies.
We suggest implementing a code change to compare the domain of 'web_url' to the self-hosted GitLab domain provided by the customers. The customer's self-hosted GitLab domain should take precedence.
1 vote -
Allow deployment of 'Check For Matching Records' in Flows.
As part of the new Salesforce Summer ’24 release, Salesforce have added the ability to check for matching records when using a ‘Create Records’ element. We’ve used this useful feature in various locations within our new flows to identify existing contacts for example.
When deploying the flows using this feature between developer environments via Pipelines or Compare & Deploy in Gearset, we’ve noticed that this new setting within the element doesn’t get deployed and is switched off in the destination org.
In the meantime, we can manually turn on this feature in the destination org.
1 vote -
Allow disabling of "Caching metadata for faster analysis"
Often this stage of the process seems to take much longer (upwards of an hour) than retreiving and analysing did in the first place.
It's unclear where this is even being cached, i've been told its in my own browser but this cant be true for a CI job with no browser available.
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 -
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 -
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 -
Fix CI PR Search Bar
The Search Bar in the CICD Pipelines appears to be using a custom matching logic that is awkward at best and outright misleading at worst. I start searching for a PBI with a term like '1093' and get 1 result, In then add an additional 3 to it ('10933') and am presented with 3 results, none of which have the term '10933' anywhere in them.
The algorithm appears to chunk parts of the search value and then 'fuzzy match' using each 'chunk' of string. So by adding a 3 to 1093, I was all of the sudden searching for all…
1 vote -
Recognize code formatting changes as differences that can be deployed
If an Apex Class or other code file has been modified to fix formatting only, changing the indentation size for example, Gearset doesn't recognize this as a change that can be deployed. Formatting changes are recognized by git and SFs own source tracking feature so it should be recognized by Gearset.
2 votes -
Add RecordType support for PersonAccount
Problem analyzer is always trying to remove my picklist values from any RecordTypes on PersonAccount. I am forced to use a custom "Problem analyzer template" where "Remove picklists from record type" is disabled.
Suppose I have a field called pickme: Account.Pickme--pc | Contact.Pickme--c it shows up in the record type XML as Pickme--c, and it seems like gearset tries to find a picklist on account with that exact API name, which will of course fail. My ask is that rather than raising an error at this point, GS should repeat this check on the contact object where it would find…
16 votes -
'Continuous integration' menu item links (redirects) to Deployment Pipelines
When I click on 'Continuous integration' in the left menu it goes (redirects) to Deployment Pipelines (https://app.gearset.com/deployment-pipelines?pipelineId=xxx) by default since a week or so! 👎
I just want that menu item to keep on going to the 'Continuous integration dashboard' (https://app.gearset.com/continuous-integration).
What's in the name (of the menu item)! 😉1 vote -
Prevent deployed validated packages from being deployed subsequent times
Currently, after you deploy a validated package it no longer appears under the Validated Packages menu, however, if you still have the link for the validated package and navigate to that package it doesn't give you any indication that the package has already been deployed and allows the user to click the Deploy button again, assuming they have deploy permissions on the target org connection.
As part of our production deployment approval process, we store the link to the validated package in our external ticketing system (https://app.gearset.com/validated-package-details?deployPackageId=<package id here>). When completing the ticket, users use that link to…
1 vote -
Search on comparison doesn't search though object child items
When searching on the comparison results screen the child items of an object are not part the search unless you expand the object.
If you expand and then collapse the object tree child items do then appear in the filter search. It appears to be just on initial loading that it doesn't work.
4 votes -
gearset doesn't seem to pickup date of change for custom field and custom metadata.
gearset doesn't seem to pickup date of change for custom field and custom metadata.
2 votes
- Don't see your idea?