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.
1240 results found
-
Re-validate a deployment after failure without returning to compare
Would love the ability to re-validate a deployment after making changes to the target org. I notice this a lot if there's a username issue that needs fixed in the target, I'm able to fix the issue without refreshing the comparison, but still have to return to the compare, go through the automated fixes, and then re-validate the deployment.
2 votes -
Add Salesforce ID to Export History button
Can you add the Salesforce ID to the Export History button for reconciliation purpose.
We currently have to manually match the Salesforce ID in Gearset with the Salesforce ID on the Salesforce Deployment Status page to get the reference between the source ticket in Jira and the deployed change for compliance purpose which is a time consuming process.2 votes -
Ability to return sub-components of a Profile from Source Control
Currently, profiles in source control are stored with everything as it's all stored in a single file (apex class permissions, layout assignments, etc). This is done by Salesforce.
When using the new "delta deploy" or any comparison that doesn't include every possible dependent component (ex. apex, layouts, etc) - you see many "new" or "deleted" items related to the fact that source control returns everything within the profile whereas Salesforce only returns specific permissions based on the retrieved components.
It'd be great if Gearset could replicate this behavior with source control to match Salesforce's behavior, where it'll obviously have to…
2 votes -
Allow export of code coverage results in daily Unit Testing job
It would be great to be able to export the list of unit tests and their respective code coverage in a csv file for further internal processing.
2 votes -
Allow orgs to be grouped in folders
On the “My Connections” page, I'd love to see an option to add a folder (and sub-folders).
Currently, there are options for "Developer orgs", "Sandbox orgs", "Production orgs", and "Scratch orgs".
If you are running more than one entity, having the sandboxes related to a single entity inside of a folder would be more user-friendly than having multiple dev/sandbox orgs inside the same folder.
For example, if I'm managing deployments for "ABC Company", "XYZ Company", and "LMNOP Company", and each has multiple sandboxes, it would be really convenient to be able to separate out their various sandboxes more effectively, into…
2 votes -
CI/CV job archiving
Create a mechanism by which CI and CV jobs can be archived, but not deleted. Sometimes there is a job that is not used, but the history needs to be kept for some period of time.
2 votes -
Additional options for updating Azure DevOps work items
For example, we do not want to see messages posted for validation started, validation completed, deployment started, deployment completed. We only want to see messages posted on successful deployment. And one more thing is to update the State once the deployment completes successfully.
2 votes -
Modify files during deployment process
In Salesforce, if you add an image to a PathAssistant, it hard codes the sandbox URL in the metadata. This causes failures when you then try to deploy that item to the next environment. My idea is that a feature is added that would allow some sort of find/replace logic that's applied prior to the CI compare. Something like:
File: Enter the name of the package file
Search Text: The text and/or regex string to search the file for
Replacement Text: The text to replace found the text withIn this way, it would modify the source file prior to…
2 votes -
SFDX projects and source format and CLI useage
Gearset CI only supports SFDX source that follows the SFDX project template structure (e.g. force-app/main/default/classes and so on). However, SFX CLI doesn't mandate that structure.
SFDX allows you to group metadata by function or logical group (so you can combine metadata in any way that makes sense to you) . We have many projects like this that gearset cannot deploy.2 votes -
Checkboxes to delete multiple packages/validations/deployments at a time
Hi - feature request:
Checkboxes on the validated packages (and probably others) screen so that I can delete validated packages more quickly. One by one is a big pain, and it probably uses your storage... and it definitely clutters our workspace.
Thanks!2 votes -
Create a persistent default setting for Monitoring Job Notifications
It would be nice if there was a way to default the notification for monitoring jobs to 'send notification only when changed'. Right now, if you set monitoring, you get an email a day from that job, regardless if there was a change or not. You have to manually change it otherwise.
Nice to have that setting front and center, available when you select monitoring, as well as have a default value for each org type; Prod, Sand, and Dev.
2 votes -
add the ability to filter Git repos on connection
It would be useful to be able to select only applicable Git repos from source control that will interact with Gearset. A user may have many repos that they need on their account, but of those there may only be 1 which would be used via GearSet. It would be great if we could select which repos should be available when setting up the connection to our source control (specifically I am requesting GitHub but I think this would be useful for all source control integrations).
2 votes -
Display Permission Set changes as one entry
When working with Permission Set changes, it sometimes would be useful to see them grouped by Permission Set instead of being disaggregated by field. For example, we are migrating from using Profiles to Permission sets to grant all access. Currently, if we make changes to many (>100) fields in two different Permission Sets, we have to review many (>100) entries. Also, grouping by permission set would allow us to deploy changes to one Permission Set while ignoring the other.
2 votes -
Connection List Search Feature
Add a Search feature to Connections Page. I have 59 connections at the moment and the only differentiation between them is a suffix at the end of the login. It would be nice to be able to quickly search the list of Connections like a CTRL + F would do.
I often have to scroll the list and compare login usernames.
2 votes -
Set values on record creation for fields that can't be updated
Some objects, for example PriceBook Entry, must have their attributes set on insert as once created most of the record is not updatable, e.g. CurrencyISOCode cannot be changed on this record once it has been inserted. Providing a way to set these fields on creation, rather than a later update step, would allow these records to be deployed as currently PriceBook Entry records fail in multi-currency orgs as they are all created with the default currency causing SF to treat them as duplicates
2 votes -
Problem Analyzers don't evaluate changes made from other Problem Analzyers
Even though this example has an easy workaround, it does seem like a scenario which could present issues in other deployments.
In the scenario where a standard application that doesn't exist in the target (ex. Sandboxes and LightningInstrumentation) is included in a deployment (along with its permissions), there's 2 problem analyzers that come into play
"Remove standard application additions/deletions from deployment"
"Remove items which reference the listed components which are not available in the target"
When both metadata types are selected (application and permission) only #1 is flagged. This means Gearset removes the standardApplication, but leaves the references to the…
2 votes -
Add support for deploying a name change to a SFDC component (such as profile)
We occasionally change profile names during permssions clean-up projects. Currently, when you deploy a profile with a changed name, Gearset recognizes it as a "new" and a "deleted" profile, instead of a single "changed" component, which makes the deployment challenging.
I know that the name is used as an identifier, since the Id may not always match between source and target. However, if you add support for this, the tool could try to identify components with name changes by looking for the same Id in source and target with a changed name.
2 votes -
Allow Source to choose multiple Branch for CICD Validate/Deploy
when choosing source as GitHub it allows user to choose feature/*** which allows every commit on branch name starts feature will trigger the CICD
2 votes -
Deploy on pull request creation
Currently is supported only validation on pull request creation. It would be great if we can also do deployment on pull request creation, not only on merge.
2 votes -
Remember last used repository and branch for Azure DevOps integration
Remember the last used repository and branch in all places.
2 votes
- Don't see your idea?