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.
1289 results found
-
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 -
Monitoring enhancement: compare permissions across users
It would be cool if the Gearset Permissions Explorer would help you in determining how to collapse Profiles into fewer numbers. The model would be https://perm-comparator.herokuapp.com/
A typical org has proliferated Profiles over the years, many only slightly different from one another. As SFDC wants us to move to Permission Sets, job one is to collapse the profiles into as few as possible - this requires comparing user permissions against each other (you can't just compare profiles, you need to know what additional permissions some users have vs others too)
Since SFDC is finally making dynamic Lightning pages GA (for…
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 -
Avoid spurious differences in LeadConvert
SFDC seems to retrieve the lead convert settings in non-deterministic order between orgs . Display only true changes/adds/deletes rather than differences in ordering of the mappings as they make no difference to the runtime execution of Lead Conversion
1 vote -
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 -
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 -
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 -
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 -
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 -
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 -
Cloning deployments: add namespace option
If you are using Gearset to develop for a 1GP managed package:
Your deploys between VCS and dev orgs/scratch orgs DON'T use namespace in the metadata filter
Your deploy from VCS to Packaging org MUST USE namespace in the metadata filter - otherwise, everything in the difference viewer appears as NEW rather than CHANGED (if truly just edited during dev cycle)
So, when cloning a deployment, one should have the option to add the namespace to the clone dialog.
Without this, one has to repeat the Compare step thus losing the benefit of what you had enumerated in a prior…
1 vote -
Spurious difference CustomObject excludedstandardbuttons ordering
SFDC has a tendency from release-to-release of reordering the excludedStandardButtons for a CustomObject. If you are using source control populated under Vx and SFDC changes the ordering in Vx+1, your custom objects all show up as Changed in the differences viewer.
Because these are "excluded" buttons, their ordering in the XML file doesn;t matter to the end deployment and the variance should be suppressed in the difference viewer.
1 vote -
Use exact filters of Automated Job
Currently automated CI job filters are unique to that job and not available as a filter for manual jobs.
Ability to use the exact current job filter as a filter outside of the CI job.
Ability to to clone the CI Job filter into a new named filter.1 vote -
no difference report
Currently the deployment report that is attached to the Jira ticket includes all "No Difference" components which I don't believe provides any real value. In my instance, this includes endless amount of pages, from what I can tell the changed values I'm actually looking for don't actually exist. I would suggest either excluding from report all together or providing a summarized statement that is just a grouped item for all items that were included in deployment but had no change. Also the report should bring the actual changed items to the top of the report like it is on the…
1 vote
- Don't see your idea?