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.
1380 results found
-
Download Package Option does not include custom fields.
Just wanted to flag that the Download package option would be so much handier if it also included custom fields. Even with custom fields selected in my comparison, the package.xml that I can export only includes the Objects.
1 vote -
Allow multiple connections to the same source control system
Currently you can setup as many salesforce orgs as you would like as a source/target but you do not allow the same with VCS/Source control systems.
For example, I can only tie a single account to a single bit bucket. What if you have muiltiple bitbucket accounts that have different accesses to different repos - there is now way to do this in gearset.
You should expand the source control systems to be just like the salesforce orgs - you can configure and share as many as you would like for the same or different systems.
1 vote -
1 vote
-
allow configuration of problem analysers for different target locations
If we could turn of problem analysers for specific locations (e.g. Git repos) this would allow us to remove irrelevant problem solutions from our git commits, but keep them for deployments
1 vote -
distinguish between components of feature branch and what is syncing to main
As a user of gearset deploying pull requests to multiple environments
I want to be able to identify actual components of the feature branch vs. what is included for syncing to main/main branch for the org being deployed to
So that there isn't the confusion of understanding what new/changes items are showing up in the commit information1 vote -
Create a link in the main menu under Data Deployments for managing Data Deployment Templates. It is not very intuitive to manage them curren
Create a link in the main menu under Data Deployments for managing Data Deployment Templates. Having to start a deployment in order to manage the templates is not very intuitive.
1 vote -
Automatically Defer Sharing Calculations
Salesforce has a feature to "Defer Sharing Calculations" ( https://help.salesforce.com/s/articleView?id=sf.security_sharing_defer_sharing_calculations.htm&type=5 )
It would be awesome if Gearset Pipelines could have an option to utilize this, if sharing rules are included in Deployment, defer sharing rules for any validation / deployment, re-enable and recalculate after deployment
1 vote -
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 -
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 -
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 -
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 -
Improve Deployment Information in Notifications
I've tried both Email and Teams integrations and the actual information in the message (or attached PDF for Email) is lacking, with only great piece being the branch name.
An option to get advanced details that could provide some of the below (but not limited to):
- Actual Links - Atleast with Gitlab Self-Managed, we just get a text-based message referencing a merge request.
- Commits / Original MR - For those deployed via a Pipeline, getting the original MR (our pipeline is dev org > QA > UAT > Staging > Production, with the Dev Org > QA being…1 vote -
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 Automated Pipeline MRs
The MRs that get opened for pushing the same work through pipeline aren't very helpful. Would love to link back to the original MR which would have more of the "approvals". Right now we end up having to re-approve everything like its from scratch. Insight and auditability (maybe even bringing up who approved the original MR/etc would be great)
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
- Don't see your idea?