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.
1357 results found
-
allow users to customize Slack notifications
It would be great to have some ability to customize the notifications, specifically:
- change sender/title. right now it just shows up as my name.
- add a link to the monitoring history to allow wasy one-click into monitoring reports to see what specifically has changed.1 vote -
Add Validate pull requests for custom git
We have self-Manged Gitlab as a git provider.
It would be good to have the possibility to allow to run validations on pull requests for custom git repositories orsupport on-prem GitLab (submitted as https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39728857-add-validate-pull-requests-for-on-prem-gitlab)
7 votes -
Workflow failed to deploy without error, due to standard object dependency
In a CI job : Validation shown as success & Deployment shown as success. But actually no workflow deployed due to it being removed in the Problem Analyser.
The Problem Analyser triggered due to the (standard) object, that the workflow depends on, not being in the comparison results.
In a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap - problem analysers should never fire on object dependency.
1 vote -
Keep the same record owner between source and destination orgs.
Alternatively, allow the change of record owner before importing data to destination org.
1 vote -
Automatic retry for Unknown Error in scratch org creation
When creating a new scratch org from either the Gearset UX or via a CI job, one often gets the Unknown Error message
Gearset should attempt to retry this error as often, a simple retry works. This is especially important for CI jobs which should not have to be attended to manually.
Of course, the better solution is to not get this error at all
2 votes -
Add Static Analysis Notifications
For org monitoring, we can get a notification on either every run, or when the org changes.
Could we also have the option to get notification when the number of static analysis problems increases?
2 votes -
add files to a gitignore during Suggested Fixes
When I make a comparison, Gearset will helpfully check the deployment and offer suggestioned fixes, such as... exclude object components belong to managed packages. now, i can agree to that solution and exclude those files, the problem is they persist every time i make a comparison, they always show up as changes. Would it make sense to be able to add them to a list of ignored changes?
1 vote -
The option to auto-populate FLS/permissions for selected fields/objects/classes
I'd need an option to auto-deploy FLS for items i've selected in one click.
Sometimes the amount of changes is huge, and finding and clicking Permissions for selected items one by one is not a deal. For sure, it's possible to select all Permissions in Source org, and let the wizard to deselect Permissions for missing items in target, however that the result does not usually correspond to items that are in package.4 votes -
create an option to have chained deployments
create an option to have chained deployments so complex deployments can be broken down and sequentially deployed or slaves can be ran
allowing for multi staged deployments under one CI job
43 votes -
Explicitly set object-level permissions, even if these are omitted from XML provided by Salesforce API
Valerio recommended that I post this suggestion following a discussion on 29 August 2019.
Issue reference:
https://docs.gearset.com/en/articles/3226459-a-note-on-deploying-custom-object-permissions-on-new-profilesIssue:
1. Remove all object-level access for "Lead" from a custom profile in a source org
2. Deploy this profile to a target org
3. The profile in the target org will have access to the "Lead" object ENABLED, because this access is included in the Standard User profile (see document link above)The workaround (deploying and then deploying again) is cumbersome and not always practical, e.g. if making automated, one-step deployments outside of Gearset. Failing to make a second deployment means that…
25 votes -
Exclude the subcomponents of the parent Workflow metadata and also exclude list views from custom objects
I want to exclude outbound messages from workflows as we will have different urls in different sandboxes. Same with list views we want to exclude them from custom objects so that we can use CI using gearset for deployments
1 vote -
Enable tracking / comparison of code not in the force-app/main/default folder
SFDX officially supports tracking of source within the same package in more than one folder. The "standard" folder may be used, but you are also able to create a folder hierarchy that's more akin to a "modularization"
It can for example look like this:
force-app (any names goes here)
-> main
--> default
----> aura / classes / pages
-> module1
--> aura/classes/pages
-> module2
--> aura/classes/pagesCurrently, only the metadata inside the force-app/main/default folder is seen. It would amazing if git integration could take other folders into account too. Both for Deployments from and to Git (for…
2 votes -
Schedule multiple gearset deployments
Have the ability to schedule metadata deployments along with data deployments. As of now, you must deploy all metadata then move into data deployments. It would be great to schedule these items in some sort of task flow.
2 votes -
Option to choose CI validation run behavior with Open Pull Requests and Branch updates
Currently, if you have a CI job set up to validate based on events (push, pull request) on a specific branch the following occurs:
You open a pull request against the specific branch noted in the job - CI validation runs
You push a commit to the source branch of the same open PR - CI validation runs
You push a commit to the target branch of the same open PR - no validation runsIn the conversation with Dan on 8/13/2020, I was told this is by design on Gearset's end (to ignore that situation) to avoid long queued…
1 vote -
Only show JIRA tickets with specific statuses
We would like to the ability to only display JIRA tickets with specific statuses (e.g. Approved, In Progress).
1 vote -
One stop shopping for scratch org creation
Too many steps to get a scratch org usable for use - especially when compared to a CLI script.
If the model is VCS -> Scratch Org, then the following should be doable in one step:
1 - Create scratch org
2 - Populate scratch org with metadata in VCS
3 - Populate scratch org with SObject tree data from VCS (optional)By definition, the scratch org is empty so with a properly configured filter, the VCS metadata is implicitly all NEW and can be preselected checked
If the VCS contains multiple packages, then the pipeline config could identify which…
2 votes -
Options to pick only selected custom labels metadata for salesforce.
Since the custom labels metadata can’t be picked individually, the Gearset compare and validate process would pull in all custom label changes. This would be a concern if we want to withhold any particular custom labels from being pushed to higher environment.
6 votes -
Deploy Einstein Datasets from one org to the other
Copying of Salesforce objects with relations is a great feature. But this does not support Einstein datasets to be copied from one org to the other. It is critical for teams to have Einstein dataset in the lower orgs for development and testing
1 vote -
Include the static code analysis report in the deployment notes so it can be integrated with Azure DevOps
We would like to have a link in the Pull Request or Azure DevOps work item to the static code analysis report so the tech leads can review the report.
2 votes -
Support package.xml filtering when using Git comparison with a SFDX folder structure
When using a git repo with a SFDX folder structure + package/xml (in the /manifest folder) gearset dos not take into account elements in the package.xml when checking the option (filter with package.xml)
41 votes
- Don't see your idea?