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.
1139 results found
-
Eliminate unnecessary XML reformatting in git
Currently, when gearset deploys XML to git, it seems to run it through a reformatter, which creates superfluous changes in git. These changes cause extremely large deltas, which are hard to read, increase the difficulty of merges and the likelihood of conflicts, and make working with any other metadata tooling (like SFDX) difficult.
For example, here is part of a delta gearset commited for a profile.xml:
diff --git a/force-app/main/default/profiles/Commissions.profile-meta.xml b/force-app/main/default/profiles/Commissions.profile-meta.xml
index 8b11e6b7..3d640a50 100644
--- a/force-app/main/default/profiles/Commissions.profile-meta.xml
+++ b/force-app/main/default/profiles/Commissions.profile-meta.xml
@@ -1,10 +1,27 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<Profile xmlns="http://soap.sforce.com/2006/04/metadata">
+<?xml version="1.0" encoding="utf-8"?><Profile xmlns="http://soap.sforce.com/2006/04/metadata">
+ <custom>true</custom>
+ <profileActionOverrides>
+ <actionName>Tab</actionName>Note that it lowercased…
3 votes -
Add option to suppress managed custom fields in comparison results
When comparing Custom Objects that contain the managed custom fields there is no way to suppress the managed custom fields. The fields would show up in the comparison results even without being requested. The problem analyzers then highlights and remove these managed custom fields.
This is cumbersome when repeated and makes finding genuine differences we care about more difficult.
From the problem analyzers, it sounds like Gearset is able to identify the managed custom fields. Therefore could there be an option under [Include managed package] in the Custom Filters that allows the suppression of known managed fields in comparison results?
7 votes -
Create an rss or atom feed as you add new features
When working inside of Gearset, it often alerts you to changes that have been recently made. It would be nice to have these as a separate, consumable, feed. We have a slack channel that we would like to pipe those changes to, for instance.
1 vote -
Adding Custom destructive
ANT is unable to change the type on an EmailTemplate from HTML to CUSTOM. To solve that we need to add the EmailTemplate first to the destructive package to have it removed and then add it again with the package.xml
Since this file is not deleted but just changed. It doesn't show up in the deleted items tab.We should add an option to the "Selected Items"/"Changed Items" list to opt-in for adding that to the destructive.
12 votes -
Support merge fields in outgoing webhooks of CI jobs
When sending an outgoing webhook, I'd like to be able to include if the job succeeded, the name of the job etc.
11 votes -
Possibility to deploy to another sandboxe when a ci job passed
When configuring a CI job, we need an option to set a deployment to another sandboxe when the deployment or test classes run successfully in the current CI Job.
Ex: when a push to a branch on VCS triggers a CI job to deploy to a sandboxe like QA (with test classes run), we also have the possibility to set an auto deployment to staging sanboxe when the the job on QA passed successfully.15 votes -
Allow searching for Org IDs in deployment history
Enable the search results in Deployment History to include Org Ids.
USE CASE: I want to see a history of all deployments into, or out of, a specific org, regardless of the usernames used to deploy.
BONUS POINTS: allow me to specify whether it's the ID of the target org or the source org when searching. ex -
targetorgid:00D1U000000sfXD
sourceorgid:00D1U000000sfXD1 vote -
enumerate unsupported metadata in Manage Custom Filters
In Manage Custom Filters dialog, Gearset should link to
a) https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_unsupported_types.htm
b) a Gearset list of Metadata API-supported but not yet GS-supported metadata typessaves devops person wondering why certain metadata can't be deployed
1 vote -
update the wording in the change notifications - objects created sounds like Salesforce objects, not individual items
We run change monitoring and were very surprised to have 218 Objects created in Production over the weekend when no one was working. It would be good to rename this to 'items' instead to make it more clear.
1 vote -
Use the information in a JIRA ticket to select the components to deploy
Instead of manually selecting components to deploy. If we have an integration with JIRA and the components are listed on the JIRA ticket. Would it be possible to then specify JIRA tickets to deploy and have Gearset automatically build the deployment package?
2 votes -
Give users the ability to update field/object permissions for specific profiles only
The issue is, when promoting from one org to another and changing either Custom Object Permissions or Custom Field Permissions and if more than the profile you want has been changed, the extra profile changes get promoted anyway. So we need a way to control which profiles get applied when promoting field and object level security.
3 votes -
push new profile FLS entries into the profile file in alphabetical order
When picking up new FLS entries, by default these are added at the bottom of the list of FLS.
This causes issues when also having save jobs picking up changes, as this can result in duplicate FLS being added to a branch.
Please update code structuring, so new FLS is added in the correct place in the MD files.
1 vote -
Show Created By and Created Date when doing comparisons
When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well
6 votes -
Approval requests for CI deployments
It would be great if there is an automated approval process to deploy the code to higher environments. If there is a button "Submit for approval", and an email sent out to approver. that we can setup. once approved, a CI job need to run and deploy the changes to next environment.
1 vote -
Don't allow duplicate fields in comparison.
If I have a field with name example category. Somehow the same field has been added to the object xml file it needs to throw an error at the time of comparison.
1 vote -
Create a way to apply a regex to all currently selected metadata types when building a filter
The regex support you currently have doesn't really allow for complex (multi-match) regex matching, which is probably ok. (this would be something like grep -e 'this' -e 'that')
If I select, say 116 of the 124 metadata types identified, and then have to apply a regex pattern to each one, it gets pretty tedious. Click-paste-apply 116 times, and then 116 again for the other half of the complex match. I'd write a tool to automate configuring a filter in gearset. :)
If I "select all" then deselect the 8 types i don't want, and THEN apply a regex to all…
1 vote -
Allow filtering by Deployment Stage/Metadata Subset during comparison
This Gearset article describes some very logical phases for performing a large deployment:
https://docs.gearset.com/metadata-deployment-guides/splitting-a-complex-deployment-into-stagesIt would be nice if there were built-in comparisons to show each subset of metadata.
For example if you were on phase 1 of the deployment you could filter your comparison to just "Data Tier" and Gearset would pre-filter the relevant metadata.
1 vote -
6 votes
-
Stamp a validated package with the username of the person who clicked 'Validate'
Currently, a validated package is created by the owner of the draft deployment package, even if someone else was the one to actually press the 'Validate' button. I would like to have the username of the person who actually pressed validation to be noted somewhere in the validated package for auditing purposes.
This would help us be compliant with processes where we need a record of separation of responsibilites bewteen users.
4 votes -
Add functionality to select the changes in the component for the deployment.
I think it will be very helpful to have a possibility to deploy only some selected changes in the modified component.
1 vote
- Don't see your idea?