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.
78 results found
-
Remove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as
Add during problem analysis:
Remove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as logged-in user"). Deploy, then change it back to whatever you need. Based on https://developer.salesforce.com/forums/?id=906F0000000DCJPIA4
3 votes -
Queue Deployments
Current State:
A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org
1st Dev deploys work to .dev
2nd Dev deployment fails because org is locked
Idea:
A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org
1st Dev deploys work to .dev
2nd Dev deployment is queued up, 2nd Dev will be notified via email/browser when queued deployment has started
3 votes -
add the ability to run static code analysis against an org or source control, simply click refresh button to re-run it and see results
This will give you a "run code analysis -> see results -> fix issues -> push to source control (or an org) -> repeat" workflow.
3 votes -
3 votes
-
Allow PMD to be configured by uploading a xml file with rules
We use PMD locally in our IDEs to analyse during development, and the whole team shares a rule file in xml. It excludes the ones we don't like and configures other rules.
We can configure Gearset to do the same through the UI, but I'd rather be able to just upload the file, then I will know they are the same set of rules.
3 votes -
Adjust dependancy on managed package versions for Apex[Class|Page]
We've found when developing classes against managed packages the class ...meta.xml includes the package version numbers. Problem is these are fixed to the exact version installed (e.g. 9.4, 9.3 etc. example below)
But then if the managed package is upgraded Salesforce, in its infinite wisdom, doesn't update these so when you come to deploy next time you have to go and manually update all the version numbers - or if you have a different version in another sandbox (to test the newer one) same thing.
Seems like something a cool deployment tool could handle and offer to fix up on…
3 votes -
Please adjust problem analyser feature to show record type changes when a picklist field value is added.
Currently Problem analyser does not show any warnings or issues when record types are not selected for a picklist field changes( value addition). With this during deployment there is fair amount of chance that some one could easily miss record type changes. Please adjust problem analyser to account this situation and show record type changes as warnings would be beneficial.
2 votes -
Add api version check validation
We have experienced quite a few errors when a metadata component is developed in a sandbox that has been updated to the preview api version but production hasn't been updated to that version yet. Our entire pipeline and PR validation process works perfectly until the very last step when deploying to production. It's very difficult to deal with at that point.
2 votes -
When Problem Analyzer adds Fields, Add Profile Permissions Too
Currently the problem analyzer will identify missing fields. However, it doesn't prompt or allow you to add the permissions for the fields. So, you either have to go back, manually add all fields as Selected, or push the package and then go back manually and add permissions for all fields. It should prompt to add both the fields and the permissions.
2 votes -
Support deployment of password and session policies via Gearset
According to the Salesforce developer link https://help.salesforce.com/s/articleView?id=000349181&type=1
Password and Session policies include a numeric code which is equal to a epoc timestamp. This timestamp will be different in each org. In order for deployment to succeed, the timestamp code in the metadata name must match the target org. Since all orgs are different, there isn't an automatic way to do this.
Please create a feature in gearset that will automatically replace the timestamp numeric code with that of the target org so that we can use gearset to deploy password and sessions policies.
2 votes -
Allow owners to setup delegated org access of members
Without already having delegated access granted there is no way to rollback a deployment from another user. There should be a permission to override this.
2 votes -
Deploy first fields where <trackHistory> was changed from true to false.
Deploy first fields where <trackHistory> was changed from true to false.
I am currently deploying fields changes and getting error that too many fields are tracked because fields with true ale deployed first.2 votes -
Option to have SCA results for last commit or Period, Instead of SCA for complete file
Hi All,
We are looking for a SCA feature so that instead of showing all the errors and warning in the whole file while doing compare or deploy, It Should only show the SCA errors and warning for the last commit or for commits during an specific time interval.
For Example I have an existing Apex class which is having 1000 lines of code and say 100 errors are there as per GS SCA analysis. Now let’s assume I am working on that file for my current sprint and I am adding another 100 lines of code in that class.…
2 votes -
Warn on Master/Detail deployment even without comparing Custom Fields
If you compare Custom Fields and try to deploy something in an Object that is in a Master/Detail relationship without including the Lookup field, Gearset will warn you that the deployment will fail.
However, if you don't include "Custom Fields" in the comparison, (for example just comparing Validations) and try to push it, you will hit an error:
"Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field"
Gearset could easily warn the user on this when trying to push a Validation Rule on a MasterDetail object, even if Custom Field was not added to the comparison.
2 votes -
Re-validate a deployment after failure without returning to compare
Would love the ability to re-validate a deployment after making changes to the target org. I notice this a lot if there's a username issue that needs fixed in the target, I'm able to fix the issue without refreshing the comparison, but still have to return to the compare, go through the automated fixes, and then re-validate the deployment.
2 votes -
Spacing in formulas
This was marked as completed in https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/34690018-preserve-spacing-in-formulas but seems to be broken again. Formulas or criteria in WF are deployed without carriage returns, which makes formulas very messy to work with.
2 votes -
Include Apex classes imported into LWC
Ensure that Apex Classes imported in LWC javascript files are included in dependencies.
2 votes -
Deployment Notes Persist on Failure
When a deployment fails, deployment notes are sometimes wiped, and it is laborious to retype them - sometimes, I'll copy and paste to Notepad before deploying because I know I'm going to have to type them again. Notes should persist, or at least be configurable, from one comparison run through successful deployment.
2 votes -
Add a note against individual components in a draft deployment
While comparing two Org's for differences and saving the 'Draft deployment':
Files that I'm sure and fine with the differences and happy - so tick them.
Files that are important to be deployed but I am yet to discuss those differences with some peers from team (dev / support). I would like to mark these (or / and) comment against these - with some useful notes (ex: impact or risk analysis related notes). Once these are discussed, I can then tick them - indicating I am happy to deploy these.
Once I mark the files as either 1 or 2…
2 votes -
When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments
When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments
The SharedTo User doesn't exist in the target org causing my deployment to fail.
2 votes
- Don't see your idea?