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.
1400 results found
-
exclude specific JSON keys when comparing Vlocity/Omnistudio metadata
We are seeing Omniscripts showing as different on certain JSON keys. These keys always change and should be excluded from your comparison.
The impact of this is Omniscript deployments require the LWCs to be compiled and if we deploy Omniscripts unintentionally, their LWCs are not recompiled and functionality breaks for the users.1 vote -
Flow equivalent of Static Code Analysis-esque rules
Code Analysis rules run against Apex in Gearset. As Salesforce development continues to rely on Flows as the main tool for declarative automation, it's becoming challenging to catch known inefficiencies, known issues, and discouraged usages. It would really set Gearset a part as a deployment tool to utilize issue detection or run "rules" against Flow metadata to call out potential issues or flows not following best practices to even prevent a deployment or commit from occurring.
Examples: SOQL or DML in a loop, the number of elements for flows (prior to api v57) or general overall complexity, lack of Descriptions…
4 votes -
Remove limitation of number of PRs to be added to a Release (Azure DevOps + Gearset)
Gearset automatically adds all PR details for a release in description box (Azure DevOps PR) which has max character limit of 4000 and only 16-18 PRs can be added to a release because of it. When we add one more PR after the limit is reached then the next PR does not get added to the Release and we need to create another release for them which is not correct approach as other releases may have some dependency on 1st and thing may fail in production. We need a way to disable adding description to Azure DevOps Release PR so…
2 votes -
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 -
Limit who can connect Production or Specific Orgs
Our users may have access to certain orgs to do manual changes (we are working on reducing, but will probably never get to 0). Ability for us to block who can connect production can enforce usage of pipelines and prevent users from connecting their own user where they would get deployment access.
3 votes -
Salesforce Data Processing Engine metadata deployment
Enable the Data processing engine component deployment via Gearset. The metadata name is"BatchCalcJobDefinition"
1 vote -
Share edit access to a CI job with another user
Currently, only the owner of a CI job is able to edit it. This is a risk, as the owner is not always available to troubleshoot CI issues. It would be helpful to be able to delegate edit access to other team members so that pipelines can be managed collaboratively.
3 votes -
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 -
Add option to "run tests if X is present" on CI jobs
At the moment Gearset only offers an "all or nothing" option ("run all tests"), which is safer but completely ruins minor and cosmetic deployments (because it then takes half an hour to deploy even the smallest, inconsequent change like a Layout change) or "apex or nothing" option ("Default") which does allow for minor deployments to go through.. but also anything that's not Apex, which is dangerous because what if I'm deploying other automations like Flows? these changes would go un-tested.
At the very least an option for "run all tests if Apex OR Flow is present" sounds mandatory. But ideally…
4 votes -
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 -
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 -
ClickUp integration would be awesome!
My company uses ClickUp to manage tickets, would be great if there was integration with Gearset as that would save me copy/pasting ticket references into the deployment descriptions.
6 votes -
Deploy Managed Custom Filters Globally
When we associate a custom filter with a particular CI job, and then make changes to the filter, give the user the option to push those changes to all jobs (list them out) that use that named filter.
4 votes -
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 -
Set Problem Analyzer to default with all rules disabled
Problem Analyzer rules are automatically enforced for CI Deployments which are misleading to end user as the default has ALL rules set to enabled. My recommendations is to have the default template have ALL rules set to disabled OR have clear communication in the CI Deployment feature to notify users that Problem Analyzer rules are enabled and may cause expected deployment behaviour/errors.
3 votes -
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 -
Integrate with Agile Accelerator instead of just Jira
Integrate with Agile Accelerator instead of just Jira.
It would be great if Gearset (and ideally the Pipelines-feature) could integrate with Agile Accelerator.Since we're a Salesforce-partner we want to use as many Salesforce-native solutions. That's why we've been happily using Agile Accelerator for many years.
It would be great if Gearset can also integrate with Agile Accelerator instead of just Jira.
Right now the Gearset Pipelines feature isn't useful to us, because of this sole reason.Thanks for considering this!
30 votes
- Don't see your idea?