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.
1405 results found
-
Allow custom endpoints for webhooks from Unit Testing and Monitoring Jobs
You can post to Slack, Teams, and Chatter when an org monitoring job runs. But, as a consultancy, we'd like to post to our own SF org in a more general way. We have records for each of our customers, and it would be good to be able to report on summary data about the Gearset's monitoring for those customers.
If there were a configurable endpoint we could target that at a custom REST endpoint on our Salesforce and then join things up.
1 vote -
Repository Rebasing
Allows the Git repository to be rebased from the latest and greatest metadata from a target organization. In just few clicks the gearset will download all the latest metadata from a target org and will check in it inside master branch
1 vote -
Allow
Once the comparison is completed. Gearset should tell us which commit Id belongs that changes.
Gearset should allow the users to deploy per branch. User will be allowed to cherry pick commit Ids then that commit ids will be package and able to deploy it.
1 vote -
Deploying to an org based on tags
It would be a useful feature to initiate a deployment when a Github tag is created.
1 vote -
Don't Delete Managed Package's object permissions from Permission Sets in CI jobs
In a CI job, using source control as the source and including deleted items, you can run into an issue where objects from managed packages show as "deleted" in terms of custom object permissions from permission sets that have access to them. This can occur for permission sets designed to give access to managed package features or if you have a permission set with "View all data" or a system permission that gives them access to all objects in some capacity (read, write).
Ideally, we wouldn't have to include managed package object permissions into Source Control (likewise, Gearset suggests only…
1 vote -
Show/Flag what unlocked package elements are getting updated on Monitoring Jobs
When you look at the details of a monitoring job there is a field called "Packages Afftected" that shows green when is 0 and orange when >0.
There is a description that says...
Unlocked packages have been modified. View the comparison to see details.
However, when you look at the details there is nothing there to see what unlocked package element was modified. So the warning it is not very helpful at all.
Can this be implemented so that the warning is actionable.
2 votes -
it would be great if deployments could be done automatically based on a event trigger
To facilitate Automated Testing, it would be great if a deployment could be triggered by an event (such as a commit by a dev), so that an org is created to allow functional automated tests (not unit tests) to be run automatically without requiring any manual process
1 vote -
Provide the option to skip code coverage when running tests on a schedule
skipping code coverage on apex test execution, helps tests finish faster.
1 vote -
Avoid manual selection of component while compare and deploy
Good to have options in Gearset to auto select changed metadata files(changed as a part of pull request) while doing Compare and deploy.
Imagine one pull request number 5377 (which is changing 200 metadata files moved from 1 branch to another branch).
Now while doing compare and deploy It is good to have options which auto select this 200 metadata for comparison. This can help me from this manual selection of 200 metadata files which is very time consuming.1 vote -
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 -
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
45 votes -
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 -
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
- Don't see your idea?