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.
1235 results found
-
Recognize code formatting changes as differences that can be deployed
If an Apex Class or other code file has been modified to fix formatting only, changing the indentation size for example, Gearset doesn't recognize this as a change that can be deployed. Formatting changes are recognized by git and SFs own source tracking feature so it should be recognized by Gearset.
2 votes -
Remove Site.com from the Default Experience Cloud Comparison filter
The Default Experience Cloud Comparison filter include the Site.com component. This component seems to cause problems with Experience Bundle deployments. I recommend this should be removed from the Default filter.
1 vote -
Add setting to skip Salesforce validation for Aura/LWC only changes
Since Salesforce tests don't cover LWC/Aura components anyhow, if the changes are all Aura/LWC the validation should be skipped.
1 vote -
Better Multi-Org Support
We have 3 separate Production orgs for our company. It would be ideal if when we logged into Gearset we had a toggle to choose which production org and then all views, pipelines, connected orgs, etc. were filtered.
1 vote -
Support Gitlab Application Tokens for CI Jobs
Gearset uses User-level Application Tokens which is great for all user-initiated requests. However, things like automated commits, new branches, etc would be ideal if we could tie to Gearset. Gitlab supports granting out tokens at the Group or Repo-level where we could provide a better and more auditable tracking of Gearset automations
1 vote -
Automated Commit Message Identifiers
It would be great if automated commits/PRs/etc had a note that called out they were automated for audit purposes.
1 vote -
ORG Deployment notification
Set notification distribution at Org level besides users profile level.
People are interested on deployments to Production for example. But not everyone is as interested if a user deployed to another sandbox.1 vote -
Display Friendly Org name in deployment - validated and history
Allow to define columns displayed in deployment. I'd like to see Org Friendly name instead of username. We defined these org friendly names when the connection was defined. I'd like to see it as a column with the Deployment dashboards. Most often we care more of the friendly name than the username used to connect.
1 vote -
Provide a list of Frequently Used Metadata Types for easy filtering
I often don't know which metadata types I need to include in a comparison so I don't miss anything so I often use Compare All (takes forever!). I'd like to have Gearset suggest filters based on past deployments so I can confidently compare without having to wait a long time.
1 vote -
Show file storage backup progression
When having large SF orgs with large file storage amount, is impossible to see the progression on the backup. You can only see the object that's being processed. For our org we've seen "Attachments" object under backup for more than 1 month without any idea on where we were.
It would be really helpful to have information on the progression of each backup object (either data or file storage).
Showing the information like: "Backing up file storage in 'Attachments' (1/12). Retrieving record XX of a total of XXX records from Salesforce". Already backed up XX GB in file storage.1 vote -
Update the layout comparison view of Page layouts to reflect custom button/button changes on related lists. Currently XML view only
The layout view does not show custom buttons added to related list/other button changes. This is visible in XML view, the layout view is slightly confusing as a result - The "Select all" tick at the top is present, but no other tick boxes, making it unclear what you are selecting unless you use XML view
1 vote -
Date to date filter
A date to date filter so as to ignore anything outside of that time window. Even if it could just be all the changes for one year, that would help.
1 vote -
Allow a PR template from GitHub to pre-populate the PR description
There is a feature in GitHub to auto-populate the PR description (forcing, for example, a checklist if using the web UI). If Gearset could read that template and pre-populate the PR description so users have to put in specific comments (such as manual steps to be done after deployment) and if that description were exposed in GitHub, then it would be more seamless and the deployment history would enable an admin to work through each manual step without looking in closed PRs in Gearset.
2 votes -
Create ListViews in the Continuous Integration Dashboard
Create ListViews in the Continuous Integration Dashboard page and being able to grant access to specific users or groups of users.
The idea is to avoid displaying specific jobs to a particular group of users for better organization and reduce the loading time when many CI jobs are configured.
3 votes -
Allow different source control users per CI job
At the moment, my GitHub user is defined at an account level. So that user is the one for all CI jobs.
I may want to have a different GitHub user for each of the projects that I run through Gearset. For example, if we are a consultancy that generally use our own stack, but have to use a GitHub user belonging to a customer on some occasions.
Or (as I do now) I may want to switch my GitHub user from one to another. Today, switching that user will disable ALL OF THE CI JOBS. And I will have…
1 vote -
Add the option to schedule weekly, monthly and yearly backups
To meet our backup compliance requirements I'd like to suggest an option to schedule weekly, monthly, and yearly backups to go along with the daily backup option that is currently available. This way, we could setup multiple backup tasks with different retention.
Thanks
6 votes -
ClickUp integration would be awesome!
My company uses ClickUp to manage tickets, would be great if there was integration with Gearset as that would save me copy/pasting ticket references into the deployment descriptions.
3 votes -
Save Filtered Metadata from a Comparison View as a New Custom Filter
When running a compare, we'll often filter the list of metadata types in the results to eliminate types we're not interested in comparing. It would be nice to save the filtered view as a new Metadata Filter for use in a future compare.
2 votes -
package missing -meta.xml endings
When I download a package from a CI Job, it doesn't include the require "-meta.xml" ending for my metadata types. I wrote the following script to add them back one folder at a time. It would make more sense if Gearset just gave me the correct filenames when I download the package though.
…# Gearset gives us a downloadable package to trouble shoot, # but it doesn't have the -meta.xml text appended to it. # Find all files with this ending and append -meta.xml to it. find ./ -type f -name '*.flow' | xargs -I '{}' mv '{}' '{}'-meta.xml find1 vote -
Sandbox Deployment With 0 Components
Running a deployment into a Sandbox or Prod that has 0 components is a waste of time and resources.
If a deployment has 0 components in it, either
1. There's a problem because I was expecting greater than zero (so throw an error), or...
2. I want to run tests, and theres a different command for that (I shouldn't be executing a deployment just to run tests).3 votes
- Don't see your idea?