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.
1361 results found
-
Add the ability to hover on the New, Changed, Deleted bubbles on the COMPARE & DEPLOY Results Screen and see the meanings
Can use the wording from the documentation :)
1 vote -
After a package is validated, link to the Salesforce Deployment ID
Gearset already does this for a deployed package, that on the Deployment Summary page it shows the Salesforce ID of that deployment. Can we provide the Salesforce ID for a validation build against a Salesforce environment as well?
1 vote -
Clickable Jira Request within Pipeline Promotion History
I would like the ability within the pipeline promotion history to make the Jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.
3 votes -
scroll bars
Get rid of the scroll bars in the open pull requests tab caused by the queue section overflowing its bounds.
Also, allow us to post screenshots here. :\
1 vote -
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 -
Audit changes to the "Require issue tracking" setting
As a result of a query by our auditors it would be helpful to have changes to the 'Require issue tracking' deployment setting audited. They are concerned that a team-owner could alter this to perform a deployment then reinstate it, resulting in change deployment without tracking.
1 vote -
Add "Open Branches" Tab to Development Sandbox Environments in Pipeline
The only way to deploy an existing feature branch into a development sandbox is to perform a manual compare and deploy. Previously, we had our developer sandboxes set up as static environments which allowed us to create PRs against them for "re-deploy". This is not possible with the new Development Sandbox format. I suggest another tab be added called "Open Branches" which will allow the developers to select a feature to pull and work on in their development environment. That way we get the benefit of easy compare & deploy instead of having to manually compare and deploy. This will…
4 votes -
sandbox seeding size
When deploying data to sandboxes, it would be helpful to get an approximation of the amount of data and file space a seeding job will need. I have on numerous occasions hit storage limits as a developer sandbox only has 200 megabytes of usable space.
1 vote -
Add an option to ignore ".forceignore" files
When a repository contains a forceignore file, deployments to that repo will not include these elements.
Sometime however it might be necessary to explicitly deploy these elements (e.g. manually).I propose to add a flag "Ignore .forceignore" at least for manual comparisons + deploys to be able to still push generelly ignore components to the repository.
1 vote -
Force API update for deployment
Please provide the ability to force API versions for deployments.
Allow the administrator to place an API version in a setting and when a deployment is validated or attempted deploy if the API version is the value or below then do not allow the validation or deployment.
2 votes -
It would be great to have a centralized way to view all components and static code analysis results for every commit within a branch.
It would be great to have a centralized view for all components and static code analysis results across every commit within a feature branch. For example, if a developer makes five commits to the same branch, it would be much more efficient to review the components and static code analysis results for the entire branch in one place, rather than checking each commit individually through the deployment history. Additionally, there should be an export option to easily share the results with developers. Thanks
3 votes -
Trigger CI Jobs on Gearset deployments
When setting up a CI Job originating from SFDC, we only have the option to trigger the job based on a time interval. Which makes sense since there are no events to subscribe to in SF for this.
But, I think it'd be helpful to be able to trigger a job to run on the completion of another Gearset deployment. This would be useful for automating the addition of metadata items like fields or layouts into source control, which are less-than-fun to create as xml files.
So rather than running such a job every 1hr, we'd ideally be able to…
2 votes -
Visibility settings for 'Shared Sandboxes' in the gearset pipeline
Currently, Gearset only supports the binary visibility settings for sandboxes; either the developer could see his/her sandbox or everyone's sandbox. But in the case of a 'Shared Sandbox,' there is no ability to give visibility access only to a specific subset of users in the pipeline.
1 vote -
Please add support for GenAI objects
Backups are currently failing when GenAI metadata objects are selected. Please add support so that we can backup agentforce related metadata.
1 vote -
Seed Data alongside Feature Branch Promotions to Orgs
The idea is to bundle the data that should be tested along with the feature branch, so that once a story is deployed the data is also available (similar to one of Copado's features).
This allows us to test regardless of dev, partial or full copy sandbox type. Allow for a set of data to go along with a feature for testing reports and analytical tools. Possibly integrate existing Seeding Templates that can be paired with a feature branch. Allow for configuration of data deployments to environments through the CI job for feature+data deployments. Allowing some environments to refuse the…
1 vote -
Add navigation into elements of LWC bundle in difference viewer
The current LWC difference viewer shows the components linearly from top to bottom - meta, css, html, js. Just like you did with the side bar navigator for layout, add a side bar navigator for the LWC bundles
1 vote -
Allow developer sandbox updates to be queued instead of failing
When you update developer sanboxes you can only do a max of 2 at a time or else the extras fail and do not automatically retry when the other are done. I would like if they would just enter into a que so that you could click update on all of them and not have to wait until the first 2 are done to then click the next two.
1 vote -
Update all developer sandboxes with one click
Deploy updates to all developer sandboxes with one click
1 vote -
Promotion PRs should show the original author on GitHub enterprise
Hello, according to the documentation here - https://docs.gearset.com/en/articles/8545155-why-are-my-prs-showing-the-pipeline-owner, promotion PRs created by Gearset in GitHub can show the original author of the PR. After talking with support, they told me that this feature is not supported for GitHub Enterprise. Could this be made available in Github Enterprise, as it is now in GitHub?
1 vote -
Promotion PRs should show the original author on GitHub enterprise
Hello, according to the documentation here - https://docs.gearset.com/en/articles/8545155-why-are-my-prs-showing-the-pipeline-owner, promotion PRs created by Gearset in GitHub can show the original author of the PR. After talking with support, they told me that this feature is not supported for GitHub Enterprise. Could this be made available in Github Enterprise, as it is now in GitHub?
1 vote
- Don't see your idea?