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.
1304 results found
-
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 -
Export Deployment History Additional Information
It would be great if the Deployment History was able to provide details from Source Control. Specifically, list of people who approved tickets, branch names, commit IDs, etc.
2 votes -
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 -
Trigger Gitlab Pipeline Faster
When opening a MR in Gitlab, the Gearset pipeline queues the Validation very quickly. However, in Gitlab, there is no pending Pipeline until Salesforce starts the validation. Sometimes this can be a lengthy period of time with no visibility inside of Gitlab.
Would be nice to trigger that immediately so approvers can see that it is queued, not just no pipeline job has been executed yet.
3 votes -
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.
2 votes -
Granular Permissions
Most of our users don't need to be doing any configuration outside of connecting their Dev Sandbox. Prefer to have more granular permissions to lock down features to smaller groups of users.
2 votes -
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 -
Gearset CPQ deployment to delete target org component if source is deleted
Example in CPQ template you have situation when you need delete from source org component (content, line column etc.)
Now you have to delete this in target org as post deployment task.
Current solution support only new or changed component change.2 votes -
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 -
Add api version check validation
We have experienced quite a few errors when a metadata component is developed in a sandbox that has been updated to the preview api version but production hasn't been updated to that version yet. Our entire pipeline and PR validation process works perfectly until the very last step when deploying to production. It's very difficult to deal with at that point.
2 votes -
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 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 -
CI job merger conflicts
When resolving CI job merge conflicts, a user has two windows to accept changes from one side of the window. Can we have an option to accept specific components changes from one side and certain changes from the other side.
4 votes
- Don't see your idea?