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.
1301 results found
-
Cleanup Layout Assignments
When you rename a Layout, the previous Layout Assignment won't be cleaned up on the Profile.
This should be cleaned by the Repo dependency cleaner.8 votes -
Include "Messages reported by Salesforce" during Metadata Deployment in the final report
During a metadata deployment, on the "deployment in progress" screen, there is a column for "message reported by salesforce".
I think these should be included in the final results screen, and perhaps in the deployment report.
These can be useful for the user to do things like make changes to their flows to conform to salesforce best practices.
2 votes -
Please add Namespace/Package name as a column in the comparison view
Currently , if I pull down metadata from managed packages (e.g. with the intention of committing the custom fields we've added to managed objects or committing the permissions we've updated) this means I get all the metadata in the comparison screen, with no way of filtering out the managed packages. An example of where this is a problem/cluttering the UI is Triggers/Classes - the contents of these is always hidden, so ideally i'd like to have a column to filter them out
1 vote -
Gearset Service Status Page
It would be very useful to see a status page for Gearset services. Similar to other service platforms like Github (https://www.githubstatus.com/) or Salesforce trust (trust.salesforce.com)
This would be great to help determine if there are issues with deployments, or if Gearset has any sort of performance degradation.
7 votes -
Ability to rerun deployments
We had a deployment in a pipeline that included a change in a managed package. the MR to the environment branch has the permission set change (access to a managed package field), but the Pipeline did not deploy it. It would be great if there was a way to "re-run" an already promoted branch, as we can't use a MR at this point to trigger, since the repository already has the change.
1 vote -
Feature vs Release, Branch De-sync
When Gearset detects that additional changes have been made to a feature branch AFTER the feature branch was already added to a Release, strange behavior may be experienced.
Coming from a git background, I expected anything on the release branch would be ready to go on my deployment, but that is not what happened during my release window.
Admittedly there were some features that had changes pushed to the feature branch after perhaps the feature branch should have been closed, namely after it was on the Release branch. However there's also an argument that we should trust whats on the…
2 votes -
Provide deployment history by Salesforce ID or My Domain
If we could have a way to quickly export all changes to specific environments regardless of user who created the connection, would be ideal.
Use case: Provide a Production OrgID and be able to export all changes across all connections and manual compare-and-deploy and pipeline deployments.
1 vote -
Make the PR Title same as the validation friendly name and deployment friendly name
This helps us find the related validation and deployment to the CI job without having to open multiple validation/deployment records.
1 vote -
Allow Jira Ticket Association Changes on Commits
Please allow the Jira Ticket Associated with a Commit to be updated once the Commit is Successful. If a mistake was made prior to commit and the incorrect ticket was entered, there is not currently a way to change/adjust the associated ticket to the correct one.
1 vote -
Add navigation options to the data deployment process
We are making use of the data deployment tool to seed our sandboxes with test data. When you execute a template it always navigates you to the last step (which makes sense). There are times however that we need to go back to the 2nd step and change filter criteria. This includes several clicks and waiting for pages to load.
Is it possible to add a navigation bar at the top that shows the various steps so you can quickly jump to one you need to update?
ie Step 1 > Step 2 > Step 3 > etc1 vote -
Integrate with Salesforce's Setup Audit Trail for Metadata Detection
Many metadata types are referenced in Salesforce's Setup Audit Trail. An alternate way to detect changes to include could be querying Setup Audit Trail with a Start / End Date instead of asking user to select the necessary components.
1 vote -
Create a Combined view of Monitoring and Pipeline with Alerts
Monitoring is great, but doesn't have a correlation to Gearset deployments (direct or Pipeline).
A view of all changes to org and call-outs of which were Gearset-driven and which were manual would allow us to use Gearset more directly in SOX audits as proof of controls.
Giving us actionable items, whether its in Gearset UI or Source Control to document review and approval of manual changes would be a huge win.
1 vote -
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 -
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
- Don't see your idea?