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.
1319 results found
-
Sort or Filter Active CI Jobs
Currently, there is no great way to filter out old/inactive CI jobs from the Active CI jobs. This poses a problem as there are situations where we have replaced CI jobs in the past, or created/disabled test jobs. Currently they clutter up the Continuous Integration Dashboard, but it would be nice if we could hide them so we don't have to delete them and lose their history.
2 votes -
Backup data search feature should allow wildcards
Current the backup/restore search feature is an exact match search only. It would be great to use wild cards or to select "contains" "starts with" "ends with" or simply allow the user to use % to achieve the same.
For example if I wanted to search for the account Willy Wonky Chocolate Factory, with the exact match I have to know the exact name, but with wild card I could search for %Chocolate% and get all accounts backed up with Chocolate in their name.
1 vote -
Write Deployment Results back to the user's Salesforce org
When setting up a deployment, it would be helpful to capture Deployment Results in a custom object in the running user's Salesforce org. Users would be able to specify a unique reference at the point of deployment, which would track through to the Salesforce org.
Information about the deployment would be captured in a Master record, with data about individual components existing in Detail records.
Org admins would then be free to leverage automation features to map the created records as they see fit.
As a consultancy that tracks our customer requirements in Salesforce, our use case would be that…
14 votes -
When merging a Pull Request that is linked to an Azure DevOps work item, indicate the user who performed the merge
Currently, when a PR is merged into an Org (and the PR is linked to an Azure DevOps item), a discussion comment is added to the DevOps item documenting the merge. However, there is no indication in the comment to document the user who performed the merge. The Author of the comment appears to be the owner of the pipeline, not the user who performed the merge. My suggestion is to either make the author of the comment the person who performed the merge, OR in the content of the comments, add a line to indicate "Merged By: [Name of…
1 vote -
retain validation history for CI jobs
When a pull request is created against a branch that triggers a CI job, a validation is run. Sometimes, this validation hits errors and adjustments need to be made to the metadata filter and/or problem analyzer template until the validation succeeds. However, once the PR is promoted and the CI job successfully fires, the validation history for that PR is no longer accessible. It would be useful to be able to retain that validation history, as it would help to do further investigation into the validation errors that were hit after the fact.
There is not always time during a…
1 vote -
Provide Audit Report of Org Connections and Who Access Has Been Delegated To
It would be great if we could pull an audit report that shows all of our Salesforce connections that are set up in Gearset and who has been delegated what level of access to each of them. This would help us to prove out segregation of duty for auditors by showing who has ever had access to deploy to production.
4 votes -
Allow automated unit test execution to run tests synchronously
When unit tests are run in parallel you can often get intermittent errors such as UNABLETOLOCK_ROW. When running tests from Salesforce you are able to specify running tests synchronously which takes longer but prevents conflicts between tests. Can this option be added to Gearset for the automated test running?
1 vote -
Validation job when PRs are raised
Requirement :
Provide option to create a CI Validation Job only with "Validate pull requests targeting the source branch" and keep "Run Job" dropdown as optional .As Of Now :
When we raise a PR, it initiates feature branch validation ( cos, we enabled "Validate pull requests targeting the source branch" ), and after that when we merge feature-branch to target branch, it re-initiates another validation job.
For us, it's like similar validation is running twice on different events from which we can't opt out.Pros :
We can handle when to validate a feature branch, instead of bundling…
1 vote -
Deploy monitor results changes to target org directly from the compare screen
I get the a monitoring results email. When I click it it takes me to the comparison screen
Right now to deploy those changes I have to go to Monitoring > Filter by name > View History > Select the right one > Deploy changes to target org.Those are 5 clicks to get to a place I just was in! It would be great if I could deploy the changes to the target org directly from the screenshot comparing screen.
1 vote -
Allow for Scheduled Comparisons
Like Monitoring Jobs, allow users to choose a source, target, and metadata filter, and schedule when a comparison runs.
The primary goal of this would be time savings. To have that data already retrieved and cached so you can go in, make your selections, and move toward deployment more quickly. Possible applications include recurring deployments, planning out your workday, etc. This addition would be for non-Integration users.
6 votes -
Local Metadata ignored if name collides across an unlocked package namespace
Current Behavior:
During PR validation of an lwc component named "utils", Gearset reports no changes and runs validation against target org with 0 components because there is a Namespaced Unlocked Package in the target that also has an lwc component named "utils". This can be seen in the "Problem Analysis Results" within the Validation Details for the PR.Expected Behavior:
Gearset should not diff my local components against components that are behind a namespace. Even when those namespaced components are in an unlocked package. Perhaps Gearset should treat namespaced unlocked package components more like managed package components.This is related…
3 votes -
edit problem analyser template
There should be an ability to edit the existing Problem Analyser Template. Else, one has to create the whole template again, re-do the changes on the template and then re-assign on all the existing Jobs which should use that template.
It is definitely going to save a lot of time and be beneficial overall.4 votes -
Add RecordType support for PersonAccount
Problem analyzer is always trying to remove my picklist values from any RecordTypes on PersonAccount. I am forced to use a custom "Problem analyzer template" where "Remove picklists from record type" is disabled.
Suppose I have a field called pickme: Account.Pickme--pc | Contact.Pickme--c it shows up in the record type XML as Pickme--c, and it seems like gearset tries to find a picklist on account with that exact API name, which will of course fail. My ask is that rather than raising an error at this point, GS should repeat this check on the contact object where it would find…
16 votes -
Implement Data migration support for nCino
nCino is a native Salesforce application for banking customers, configured using records, similar to how CPQ is configured. Deploying the data based configuration from environment to environment can be very difficult and painful. This would be a valuable feature for every nCino customer
3 votes -
quote term
For CPQ Quote Term, the name column only shows "Approved" which is not meaningful.
Please switch to using the "Name" field which is a auto generated number (e.g. QT-0209) that is displayed in the user interface and therefore a meaningful identifier.1 vote -
Add configurable email reminders for scratch org expiration.
From Salesforce orgs and Dev Hubs, it would be great if there were a setting that would automatically send an email when a scratch org is approaching expiration. This could be configurable per Dev Hub, and would help prevent data loss at scratch org expiration.
1 vote -
backup expiration
For compliance purposes I'd like to request an option to list the data backup expiration date. We are able to choose how long to retain the backup, but I do not see a place that lists when the backup is set to expire.
4 votes -
Show the status of a CI deployment on the pull request
We use merge-based deployments, so whenever a Github pull request gets merged to /main, a CI deployment job fires that deploys the content of the PR to Production.
The issue is that at the moment all Merged PRs look the same, whether the deployment actually succeeded, or failed. There's no way to tell, or even to follow progress, unless we ask people to open the Gearset job and then look at the deployments for that job etc. which is quite a bit of a faff.
Validation jobs do display on the PR whether they passed or failed, the same feature…
1 vote -
Analyzer: Duplicate child relationship name detection
Use case -
target org has child object O lookup field F1 with childRelationship = Foo
source org has child object O lookup field F2 with childRelationship = FooIf you deploy, SFDC tells you that there is already a Child Relationship Foo on O
Analyzer could detect this and warn developer before deployment
3 votes -
Analyzer enhancement - detect missing ContentAsset in CustomApplication
Given this XML in CustomApplication
<CustomApplication xmlns="http://soap.sforce.com/2006/04/metadata">
<brand>
<headerColor>#0070D2</headerColor>
<logo>MyLogo</logo>
<logoVersion>1</logoVersion>
<shouldOverrideOrgTheme>false</shouldOverrideOrgTheme>
</brand>If user forgets to select Content Asset MyLogo, Analyzer should detect.
3 votes
- Don't see your idea?