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.
1376 results found
-
Allow multiple team members to be assigned to a single sandbox on the pipeline view
Currently a single team shared sandbox can have multiple users with delegated access. However, only one of the users can view the sandbox in a pipeline view. In order to allow multiple people to see the sandbox -
Current solutions:
- Add the same sandbox multiple times and assign each to the required team members
- Or, allow all team members to see all sandboxesSuggested solution:
- Allow multiple team members to be selected via the "Assign sandbox to team member" function.5 votes -
Allow users to choose their default comparison view
Different types of Gearset user will prefer to analyse comparisons in different ways. Some will definitely prefer the XML view; others will prefer the new simplified views.
I think it would be great if Gearset allowed users to specify their default view and comparisons load with this preference.
5 votes -
Mass resolve auto resolved conflicts
Currently we have the auto resolve from previous environment feature which takes previous conflict resolution into account for a new conflict dectection run in a new environment. This is great but if I am deploying through a pipeline to multiple ORGs and the same conflicts that are auto resolved each time popup I need to keep clicking through them and marking as resolved.
I would like there to be a Mass resolve button that only resolves all the auto resolved conflicts. That way I dont have to click through each one even though everything is resolved already.
5 votes -
Add support to deploy Digital Experiences (LWR) using Digital Experience Bundle Components
Similiarly to how you can deploy metadata for non-LWR Digital Experiences (Aura templates), where you can select different metadata changes individually using Experience Bundle Components, rather than deploying all your changes at once, it would be great if that option is available for Digital Experiences running on LWR (Digital Experience Bundle)
5 votes -
jira comment after deployment
Right now gearset posts comments to Jira when validation is completed and PR is merged.
We would like to have comments also when deployment is completed.The current comment "Successfully merged PR #297 from gs-pipeline/SF-23601-preprod into preprod" tells nothing to business users, they are not aware of git, CI/CD and what this message means.
Comment "Deployment to preprod is completed" makes much more sense for them.5 votes -
Add support for Vlocity managed package vlocity_cmt__ProductConfigurationProcedure__c object
Add support for Vlocity managed package vlocity cmt ProductConfigurationProcedure c object. Currently it is not supported by Gearset Vlocity tab. Confirmed by Gearset. This limits the autonomy of products deployment for Vlocity projects.
5 votes -
Add pipeline support for CPQ
CPQ deploys to and from Github/Salesforce so it should be a relatively simple issue to include this in the pipeline deployments. You could add a checkbox or just warning to ensure that triggers are manually disabled when that is needed.
5 votes -
Environment variables - Clone
Hello Team,
We would like to have the possibility to clone already existing Environment Variables when setting up a new Environment.
This functionality will allow us to refresh and create new environments faster and prevent us from performing specific commits in branches and specific configs per new environment.
5 votes -
automatic pipeline deployment on successful validation
For Pipeline jobs, provide an optional feature (ability to toggle on/off) where if an Open PR has successfully validated on the target org, then auto deploy to target org. This is useful when propagating changes in downstream jobs. For example, once code review is done, a PR is merged into DEV by pipeline admin, but it should also automatically be merged and deployed into QA if the validation is successful.
5 votes -
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.
5 votes -
Ability to report on runtime in Gearset Reporting API and what metadata filters were used
As part of showing the amount of time saved by using Gearset (and DevOps best practices), as well as the overall current utilization of Gearset across multiple teams and Gearset instances, being able to report on the Comparison, Validation, and Deployment runtime would be extremely beneficial. Also reporting on which metadata filter was used, if named and saved/accessible, in a comparison, validation, and deployment.
This data could also be used to identify inefficiencies in the standard metadata filters used across our Gearset instances, and potentially identify clients not deploying smaller and iteratively in order to prove with data how that…
5 votes -
Ability to assign Data Deployment Entitlement through Shared Connections
We have a central Gearset Owner who setup our various orgs using a dedicated Integration User in each org. They then shared the connections with Gearset Users so the credentials remain hidden.
However, this only delegates metadata deployment entitlement, not data deployment. To allow data deployment, a User needs to remove the shared connection and set up the org connection themselves.
Data Deployment Entitlement should be managed as part of the shared connection, as well as Metadata Deployment Entitlement. This will maintain the ability for central management and also keep org credentials secure.
5 votes -
Saved Comparisons should be visible to team members
I have a team that has access to Gearset but unfortunately they cannot view the Saved Comparisons I've created. To reduce unnecessary time spent on creating and maintaining Saved Comparisons, it would be greatly appreciated if the Saved Comparisons could be shared with the team and possibly allow the owner to delegate access to the Saved Comparisons.
5 votes -
Run Flow tests during test monitoring jobs
With the new flow tests, it would be nice if we could also have these run within test monitoring jobs.
5 votes -
Customize CI job commit message
When a CI job pushes changes to source control, it always uses the message "CI deployment from job <CI job name>". It would be very helpful to be able to customize this message.
5 votes -
Approval process for metadata deployment
It would be great to have a approval process for the deployment.
For example, once we have completed the comparison and validation, we can click a button "e.g.: Submit for Approval" and an email will be sent to a list of email.
In the email, receiver can review the summary of the deployment (e.g.: source org, target org, number of changed/new/deleted components, ...) and click on a link to approve or reject the deployment.
We can deploy only when the job is approved.5 votes -
Allow the creation of CI Jobs against Salesforce orgs that we are delegated to, instead of needing to be owner.
We have 2 admins that we want to be able to create all of the CI and Pipeline Jobs, even if they don't have their own credentials in a particular Salesforce org. They have Deployment delegation, and can run compare and deploys, but not set up integration jobs.
This is then requiring us to either, provision extra licenses in each sandbox for our DevOps administrator, or have the developers create the CI jobs, which they are not comfortable with.
And, as we start the Pipeline Pilot, we would like to leverage all of the existing CI jobs, but, that is…5 votes -
Ability to recreate a reusable list or group for Deployment notifications
Every week we have a larger sized scheduled deployment for logic updates that runs after business hours. There's usually the same 2-6 people (often increasing) that want to receive an email and/or text message when the deployment succeeds. Whoever schedules the deployment has to add each one manually every time, and it would be nice to have a way to send notifications to a predefined list or group of email addresses and/or phone numbers.
It usually has to be the person that schedules the deployment, because if someone goes back to add their own email or phone to an already…
5 votes -
Deactivate email deliverability on Data Deployment
User email are masked in Sandboxes and we can mask Contact emails as part of the data deployment. This still leaves the Org Wide addresses as valid emails. If there is automation that is generating emails related to the data that is loaded, they will be delivered to the Org Wide Addresses.
It would be useful if the same script that is deactivating validation rules could set email deliverability to systems emails at the same time.
In the even that email deliverability was set to all emails in the Sandbox and not adjusted before the data deployment we would have…
5 votes -
Unable to import/export translations using .stf file using greaset
Currently gearset allows to deploy translations from one org to another org, however we do not have an option to do the translations using .stf file /excel for the fisrt time in any one of the org
5 votes
- Don't see your idea?