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.
1314 results found
-
Control When Tests are Ran Based on Metadata type
It would be nice to control when we want tests to run based on the type of changes in the triggering event for CI. Something like only run test classes on update of Apex Classes, Flows, Workflows, and Objects.
This is a bit of a patch for not having test classes fully optimized but would be helpful with orgs who have lots of profile and layout changes.3 votes -
Don't auto-select all tests when choosing "Select which tests to run"
When selecting "Select which tests to run" Gearset shows the tests included in the comparison first, but the moment all other tests are loaded, everything is selected.
When choosing this option, the tests included in the comparison should stay on top and selected, and the rest of the test should be added alphabetically but UNSELECTED.
If I'm choosing this option, I probably only want to run some tests. I think it would be much easier this way. Usually you need to run the tests included in the comparison and maybe one or two more.
1 vote -
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 -
Use package xml to populate metadata filter
I suggest to add the ability to upload the package.xml manifest files to populate the metadata filter before the comparison step of an org to git or org to org deployment.
A lot of Salesforce developers use package.xml files locally to deploy some parts of the functionality in order to speed up the deployment process.
Currently, Gearset allows you to select the components via Custom Filters, but it is slow to select about 20 components manually. Uploading the package manifest from the local machine can speed up the process very much,1 vote -
Need a Integration of Gearset & Jira , once the user story is updated in Jira , My gearset job will get triggered
Need a Integration of Gearset & Jira , once the user story is updated in Jira , My gearset job will get triggered and deploy the components related to that user story.
and once the deployment is done , update the jira ticket status as deployment done.2 votes -
Change Data Capture
When installing a Integration Platform you have to enable the Change Data Capture in order for the platform to receive notifications on changes. At the moment updates under Setup/Integrations/Change Data Capture can not be deployed by Gearset :-(.
1 vote -
Ability to use Sandbox Source Tracking features as opposed to a comparison filter
The comparison screen is great to help admins and declarative users see the changes they made. However, it still requires them to know which metadata to pull based on changes they made.
Source tracking in Sandboxes is in beta and would alleviate this concern.
https://help.salesforce.com/articleView?id=sfdx_setup_enable_source_tracking_sandboxes.htm&type=5
If Gearset could leverage this functionality (potentially leveraging SourceMember object or storing .jsons to track last modified times as local projects store) it would make the complete process easy to use for all alike (pull metadata, select diff, deploy).
5 votesWe’re currently working on a technical spike to incorporate source tracking capabilities into how we retrieve metadata. We’ll keep you updated on progress.
Regards,
The Gearset Team
-
Basic Authentication with Jira
As our local hosted Jira instance doesn't allow unnamed connections it would be great to have a basic (username + password) authentication for Jira as well as Bitbucket.
1 vote -
Archive or hide Automation jobs
On each of the Automation dashboard views (Monitoring, Unit testing, Continuous integration) it would be nice to have a way to archive or hide job. Often times previously setup jobs that are not active but would be good to keep for historical reference can clutter the dashboard.
6 votes -
csv export comparison CSV doesn't identify source and targets
When you export a comparison (e.g. selected items), the CSV has column headers for Source and Target. So, someone looking at the CSV can't tell what the source was (org friendly name/repo+branch name) or what the target was (" ")
The file name identifies the source org by xxx@example.com .... but no friendly name which is key when source is a scratch org. No identification of the target at all in the csv file name.
1 vote -
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 -
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
- Don't see your idea?