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.
1355 results found
-
Maintain version history for static code analysis rule set.
Need to maintain version history of static code analysis when creating a new set of rule ,who made the change , what was the previous version , what rules were there is previous version etc. Right now we cant even clone to create a new version and upgrade on top of it.
1 vote -
Add the ability to add "Shared Mailboxes" to "Deployment Notification."
It would be logical to have the ability to add a shared mailbox to the "deployment notifications" for individuals.
The current logic is that you need to add a user, however the only way to do this is create a SF user in a DEV org for the shared mailbox which is not clean or logical for a mechanism of a notification.
1 vote -
Salesforce Data Processing Engine metadata deployment
Enable the Data processing engine component deployment via Gearset. The metadata name is"BatchCalcJobDefinition"
1 vote -
Microsoft Teams CI Deployment Job Notifications - Add Source Commit
There should be parity with the content included with a Teams web hook notification. With Slack, the Source Commit attribute is included.
With Teams, it's omitted. Please add so this data point is available with Teams. Current output illustration.
Slack
Gearset Continuous Integration
A continuous integration run succeeded for SIT Deployment / Validation job for PR #97. The job was a validation. No changes were detected for deployment.
Source commit
5ccc5b72Teams
A continuous integration run succeeded for SIT Deployment / Validation job for PR #97. The job was a validation. No changes were detected for deployment.
1 vote -
Fix CI PR Search Bar
The Search Bar in the CICD Pipelines appears to be using a custom matching logic that is awkward at best and outright misleading at worst. I start searching for a PBI with a term like '1093' and get 1 result, In then add an additional 3 to it ('10933') and am presented with 3 results, none of which have the term '10933' anywhere in them.
The algorithm appears to chunk parts of the search value and then 'fuzzy match' using each 'chunk' of string. So by adding a 3 to 1093, I was all of the sudden searching for all…
1 vote -
Audit API - Production Filtering
From a compliance perspective, we only need to ingest production changes. It appears there are fields like 'SalesforceOrgType' on Anonymous Apex Endpoint and 'TargetMetadataLocationType' on Deployments Endpoint.
It would be great if we could filter those, even better if you could bring in Production Org ID / Name into that filtering ability and in response as well.
1 vote -
having a Release Manager role within a Gearset team
I want the ability to set specific users as release managers and only these users can deploy to a production org. Only this role should be able to create a direct authentication to production. Other roles should be blocked to create a direct authentication to production or blocked from selecting production as a target org.
1 vote -
Deploy Now and Validate Package Buttons
Presently, the Deploy Now and Validate Package buttons are positioned adjacent to each other. Occasionally, there is a risk of unintentionally selecting the Deploy Now button before the package has been validated. This can result in potential issues arising. To address this, I recommend the following actions:
- Enable the Deploy Now button only after the Validate Package process is successfully completed.
- Consider repositioning the buttons within the User Interface if both buttons share the same screen.
- Alternatively, place the Deploy Now button after the Validate Package screen in the sequence.
Thanks.
1 vote -
Need to be made aware and/or given the opportunity to view the totality of the changes prior to deployment
Heres what happened, we deployed the Metadata AND a ChatBot. As part of our deployment, we manually updated the metadatas to contain PROD relavent info (instead of ACC info that was pushed from ACC Branch)
I also discovered that there were duplicate utterances in the Chatbot which we had to remove via manual DML deletes to ensure that the Data Model was built properly.
Then, we wanted to deploy just a Field change, and did so by merging a PR containt just the Field Change into main in Azure. This, obviously, triggered a deployment and in that deployment, the metadata…
1 vote -
Allow download of XML files from the comparisons page
In some instances, we have to use the Metadata API to download XML files for analysis. However, the Metadata API is a pain to use. Even Salesforce recognizes this and suggests using a migration tool like Gearset to extract these: https://developer.salesforce.com/docs/atlas.en-us.246.0.api_meta.meta/api_meta/file_based.htm
Since Gearset retrieves these files during comparison, it would be great if there was an option to download them to a zip file directly.
Note: There is already a "Download Package" feature on the deployment page. However, we obviously can't add items to this page if there is no change between the orgs. So, if a similar feature were…
1 vote -
Ability to download/restore data in bulk
We deleted 40 000 records, now we want to download data from the backup for all of them. I can filter them, select for which I want to get it and download, the challenge is, that only 500 records are loaded by default and I can load more in a batch of 500. A lot of clicking to see all of them.
1 vote -
Add the ability to back up Salesforce Change sets
While we use Gearset for our change sets, we have time where a 3rd party developer or a new admin uses standard Salesforce Change sets. We have had an incident where Hyperforce wiped out all of our change sets in all sandboxes, it would beneficial to add the ability to the backup to back up change sets
1 vote -
Indicate from Gearset if a deployment is eligible to use Quick Deploy
I would like to be able to see from Gearset if a deployment is able to utilize Quick Deploy. This would be particularly useful for releases to production as we release after hours and our unit tests can take many hours to run. Knowing that Gearset will use Quick Deploy will increase our confidence with our release and reduce mental load knowing that the deployment will be much more likely to succeed.
1 vote -
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 -
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
- Don't see your idea?