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.
1354 results found
-
Gearset VS Code Extension
My development team spend their time in VS Code where they can see all their Git information etc. It would be great to have a Gearset plugin to stop them having to switch windows and allow them to have information at their fingertips. This could also encourage more developer use of Gearset.
May display:
- Build status
- Static code analysis issues
- View of pipeline1 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.
10 votes -
Include Pull Request title in the notification
Hello GS team,
Currently, the notifications from the pull request validations only include the PR number, I would like to request if it's possible to include the PR title.
Current Sample: [Gearset] CI validation job Validation job for PR #11111 failed
With the title in the subject of the notification, we can FW the results to the right teams automatically.
Thank you!
3 votes -
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 -
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 -
add a column for file sizes and show a warning message if over the limit (might happen deploying content assets)
Recently when deploying a large amount of content assets, I ran into a issue where the deployment would freeze on caching metadata for faster comparison.
Support told me the deployment size was too large and I broke it up into smaller deployments. I suggest adding a column with file sizes and perhaps a warning message if you exceed the deployment limits.
3 votes -
Export and Import Gearset metadata filters to other Gearset instances
This idea feels relevant to Gearset customers that are consultants or in professional services teams.
Our team will be managing multiple instances of Gearset for various clients. During the initial setup and also over the long term maintenance of those instances, it would be ideal to standardize the custom metadata filters being used. The base filters would be the same starting point for all instances, because of the references to namespaces and certain metadata types involved in our projects.
Currently, the filters will need to be part of the post-instance setup steps. It would be ideal to be able to…
2 votes -
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 -
disable the ability to delete backups to prevent malicious actors and accidental damage
A lot of backup providers offer the ability to disable the ability to delete backups. This provides protection for 2 scenarios:
A hacker compromises an administrator account and uses this access to remove backups to prevent recovery after ransomware or other attack
An administrator accidentally deletes backups that are required
If there is a legitimate use case for backups to be deleted, the ability to delete can be temporarily turned on but only by contacting support and only with the confirmation of 2 or more admins.
2 votes -
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 -
Ability to export the unit test coverage in the json format and push it to the repository automatically
The sfdx CLI has the ability to generate a report of the unit test coverage in JSON format with the default naming convention test-result-codecoverage.
I would like to be able to retrieve this JSON file and push it automatically to the repository on every unit test execution.
As an example please find a possible sfdx command to achieve it: - sfdx force:apex:test:report --testrunid 7075J00001NZBNIQA5 -c -r json -d folderDirectory #testRunID is the value from the ApexTestResult obj AsyncApexJobId field
Please find more information on the official salesforce documentation about it https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_testing.htm3 votes -
Run pull request validation against a different sandbox than the one linked to the target org
Hi team,
We have multiple developers creating PRs against a common development branch (let's call it simple, develop; developers are creating their feature branches from master, the Production configuration branch). Develop branch is linked to an integration environment (called INT). INT environment contains multiple stories which are not yet in Production (some of them might go in Production, some will not go).
I would like to get my PRs validated in a Production-copy environment (called BUILDCHK) just to get a real feedback on how "deployable" are my changes in Production, for whenever their time will come.
It would be great…
2 votes -
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 -
Add the checks on the PR for the deployment
Currently, gearset doesn't provide the checks on the PR for the deployment CI job. It would be nice to have the checks of the deployment status along with a link to the comparison on the PR, similar to how we can link out to the validation job
2 votes -
Incorporate Relationship Graph into metadata deployment
Right now is it not possible to deploy Relationship Graph metadata according to https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_relationshipgraphdefinition.htm with Gearset. This metadata is required for the so called Actionable Relationship Center, which is part of Financial Services Cloud. Even though the meta data is available in the Vlocity filter in Gearset, the items we are looking for doesn't fall under that one. If selected, no meta data get retrieved and therefore no deployment happens.
6 votes -
"Sync environment" automation
On the pipeline, the action of "Sync environment" is currently a manual action. It could be useful to have an automation of this action (like the back-propagation) after each Production Deployment. This step is a little bit time consuming and can be easily missed. If we had an automatic creation of this synchronization PR on each CI Job it would make the processus more fluid.
4 votes -
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
- Don't see your idea?