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.
1138 results found
-
create a compare/deploy function for data similar to metadata
having something like new/different/deleted for data (so we can compare, say, products vs new product options or features) like we do for metadata
5 votes -
Export test run history
Exporting the Test run history to Excel/CSV will allow keeping trends.
The ultimate goal is to include this in a dashboards. If an embedable web page could be generated with solely the trends, that would be perfect.
2 votes -
Find/Replace before deployment
Allow a basic find/replace to run against files before final deployment.
Examples: a username that would work in the sandbox that does not exist in production and we need to change it. Or deploying to a packaging org required a modification due to various namespace issues. Other tools have a means to do this in one way or another.3 votes -
Distinguish between code changes and just API metadata changes for Apex in Comparison Window
For large code comparisons, it'd be great to have the ability to see when it's just a change in API vs. actual differences. Right now, you'd have to click on every row to see what the actual change was.
2 votes -
Webhook trigger when Pull Request is Completed in Azure DevOps
Continuous Integration job to trigger when a Pull Request is Completed in Azure DevOps
2 votes -
Deploy permissions for Lightning Record Pages
provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.
4 votes -
Improve the UI around deployment objects dependent on objects not in the comparison
Deployment of certain types of objects requires that other objects on which they are dependent be included in the deployment. If the needed objects have not been included in the selected items and they are not part of the comparison, Gearset will display the following message:
Problem: Some itmes reference componnents that were not downloaded from either the source or the target.
Solution: Removing the elements that reference missing components from the affected items will make the deployment more likely to succeed.
Below this is displayed a table with a column of checkboxes at the left and three additional columns:…
1 vote -
Ability to specify test suites when deploying apex classes. It would be easier when there are a large # of test classes involved.
Ability to specify test suites when deploying/validating apex classes. It would be easier when there are a large # of test classes involved with a deployment
11 votes -
Clone Package - keep Tests list
It would be great if when cloning a deployment, it can keep the tests which got performed in the original deployment. Right now, we need to keep a list of the tests which ran on a doc on the side.
3 votes -
Support VS Code extension: ForceCode
Can you please support VS Code extension (ForceCode) source format so that we can use the extension to commit and include in CI jobs.
1 vote -
Ignore sfdx-project.json file in order to compare code using Metadata API structure
I need use the sfdx-project.json file in order to integrate with VS
code, but using Metadata API structure.
Apparently, Gearset is looking for this file to define if is a metadata API or SFDX structure,So I need a ignore looking for this file, in order to compare as metadata API structure.
Thank you.
1 vote -
When Field is Deleted Permission Set changes are not recognized for the Field
Let's say we have only one object in the system. Addressc. And we have one Permission Set -> "System Administrator" with only "FieldPermissions" for all fields in the "Addressc" object.
Now I wish to Remove 2 Fields from "FieldPermissions" of the "System Administrator" Permission Set.
1st Field I'm removing just because I do not want the permission to be in the Permission set
2d Field I'm Removing from Permission Set, as I have physically deleted the Field.On Compare And Deploy Page I will See Deleted Field and I will see only one Section to be removed from…
6 votes -
Display "No Difference" metadata sources on Deployment Summary page
On the "Deployment Summary Page" it would be great to add a column to the list of metadata components added which shows for the "No Difference" items showing the source piece(s) of metadata which is causing this "No Difference" to be included.
This would dramatically help in the narrowing down of why a piece of metadata is included - especially if that piece of "No Difference" is a managed package and cannot be altered. In a large deployment, trying to identify a root cause for why a component was added is quite difficult. Simply giving a way to track back…
1 vote -
Categorize Meta Data Filters
Allow the custom meta data filters to be categorize or put in folders. You could organize your filters by customer, deployment type, etc..
4 votes -
Email2Case Deployment for Selected Email2Case Setting
When deploying email2Case i am unable to choose particular email2Case that i need to deploy and end up choose all the email to case settings. Needed feature to deploy this selectively.
1 vote -
Provide more detail in Monitoring notifications
Right now, the Monitoring job notifications (Slack especially) provide very little detail as to what actually changed.
Ideally, I'd be able to see right in the message (or in a threaded reply), the first X number of metadata changes made. If there are more than that, then providing a direct link to the detail page in Gearset would be great.
As of now, it simply just says "there were changes", with no detail or way to easily see the changes in Gearset...which is not terribly useful.
4 votes -
Use triggering branch as source branch in git-sourced CI jobs
Currently:
We have to define a single fixed source branch in a CI job, when it has a Git-Source.Desired:
Option to say "use triggering branch". It should use the branch, where current commit-hook-call comes from.It should allow Pipelines to test also all development branches e.g. with "Validation only" CI-job.
11 votes -
Plain text list export of metadata
There are times when I'm in an email thread with other developers and I want to share a list of metadata that I'm trying to deploy via Gearset. It would be nice to have a button after a validation or deployment (failure or success) that copies in plain text a list of everything in the deployment. The list not only has the name of each metadata, but also the type of metadata it is.
1 vote -
Allow Data Deployment to filter lookup fields on fetched data
Currently, when doing a data deployment Gearset will let you know of all the referenced objects from the object you selected. What it doesn't do is the opposite of that - let you know all the objects that reference your object with a lookup.
It'd be great if we could add a filter to utilize some data pulled in a fetch/query during data deployment.
ex. field (TeamMember.ProjectLookup_c in {returned Project results in query in previous step of data deployment).
6 votes -
Improve error handling for invalid XML metadata files
Currently, when there is an error with an XML metadata file (usually introduced by git merges), Gearset will produce an error, either in the Initializing Comparison, or Checking Deployment stages, stating simply that "An unknown error occurred."
If Gearset instead ran the XML from source control through an XML validator using the Partner WSDL XMLSchema, then we could get file-level validation errors if the XML doesn't conform to what Salesforce's Metadata API will accept.
e.g.:
$ xmlstarlet val -e -s ~/Downloads/salesforce-schema.xml force-app/main/default/profiles/Marketing.profile-meta.xml
force-app/main/default/profiles/Marketing.profile-meta.xml:17108.15: Element '{http://soap.sforce.com/2006/04/metadata}field': This element is not expected.
force-app/main/default/profiles/Marketing.profile-meta.xml - invalid1 vote
- Don't see your idea?