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.
1142 results found
-
Changed by and Changed Date not populating from DX structure in Repository
Using the DX/source structure in a repository (Github), no "item changed" date is shown for any metadata types in the comparison window.
This leads to gearset not being able to provide last changed date or who last changed anything in a Source DX repository. It's left with "unknown" and makes our comparisons and selections more difficult when users rely on that information.
1 vote -
Ability to override custom metadata field settings per org
Our code repository currently contains the custom metadata settings from our development environment. When we deploy to production, we either ignore custom metadata in Gearset and manually add any new custom metadata items to production or we manually select the new custom metadata items in Gearset and then manually update the fields in production from the development settings to the production settings.
It would be great if there was something like the Octopus Deployment tool has where you can define configuration settings for each environment. Gearset would automatically update the field value based on the stored setting for the specific…
1 vote -
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 -
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 -
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 -
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 -
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 -
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 -
Reporting
have a way to dump a csv of the description of objects. i need to find a way to see what fields are encrypted.
1 vote -
Ability to see count of items per metadata type
Ability to see count of items per metadata type at the Comparison Result Page
1 vote -
On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen.
On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen. We need a quick way to make sure that item level filtering is being used on each metadata type
1 vote -
The comparison screen takes too long to load and times out with large packages.
With large packages the comparison screen takes too long to load, >15 min, and can cause Chrome browser to time out. Can we have an option to not load the details of the differences in the bottom panel, only object names and then click a button to download only difference for a particular item on-demand? I normally don't need to see the diff
1 vote -
Segregate metadata changes due to SFDC release
If I compare my production org to a preview sandbox that has been upgraded to the new release, I see some changed, new, and deleted items that appear to be due to the upgrade. For the most part it probably doesn't make sense (or isn't possible) to deploy those differences in either direction, so it would be nice to be able to exclude them or have them flagged somehow.
For example, in Winter '20 several fields were added to the OpportunityContactRole object. They show up as custom fields in the comparison. If I try to deploy them to production, the…
1 vote -
Show summary of selected Filter conditions
Would like ability to select a saved filter and see a summary of all the 'checked' filter conditions in it. Useful in verifying a filter or shared filter before using it.
1 vote -
Meta Data Searches
Ability to do a meta data search like you can in eclipse or visual studio in gearset.
For example search a custom field and where it is used within your org.
1 vote -
When opening a draft/clone allow updating the content filter *before* the comparison
When opening a draft deployment or cloning a deployment, please allow the option to update the content filter before running the comparison. As things are now, we have to wait for the comparison to finish before we can change the filter, and then we have to wait for the comparison to run again.
1 vote -
Filter (regex) on Outbound Message names within Workflows in Metadata Comparison
Our sandboxes all point to different URLs within the Outbound Message action.
We want to include workflows in our CI job that backfills production changes into test environments.
However, we cannot do this as there's no way to exclude outbound messages in the filter.
In the "Metadata Comparison Filter", you only have the option to add regex or select specific items at the object level within "Workflow".
If you apply a regex to hit the outbound message name, it doesn't actually hit that outbound message name and only searches within the object name.
You can only use regex when you're…
1 vote -
Summary pages should always include ALL changed files
I believe this to be a bug, but it might be intentional. In any case, the current functionality is, in my opinion, poorly conceived.
If a user adds a deletion to a comparison between an org and git, the deleted metadata is the only item that will show up in Gearset. However, if you inspect the resulting commit in git, you will see that the metadata was deleted along with all of the profiles, layouts, etc that had to be changed as a side effect.
I'm completely fine with Gearset detecting these dependencies and making the changes to them. It…
1 vote -
Autodeploy on git branch a successfully manual deployment on org
When a developper deploy a new feature on a sandbox it will be perfect if the deployment can be auto deploy on a branch git (and copy the deployement note, etc).
Today I use a CI job backup on the sandbox but we lost the deployment comment + the updates granulartity.
We could use also the "Clone Button" on the result deployment page but it's lost time to relaunch the comparison and the different step etc while we want exactly replicate the deployment.
1 vote
- Don't see your idea?