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.
1244 results found
-
Add possibility to save custom filter RegEx for subcomponents
If you want to deploy new fields and field level security, I want to create a custom filter that hides all profile setting except of field level security and make that custom filter reusable.
Unfortunately RegEx only works on top level elements. In this case profile names. That doesn't make sense since that would hide field level security too.27 votes -
View Grouped Successful, Validated, and Monitor Jobs per Instance in List
Our organization has now done over 13,000 deployments (yay!), but that means when I have to search for past deployments, any searching beyond 10 days as the filter becomes an impossible task because of the sheer volume that has to be searched (boo).
When trying to combine successfully deployed packages into a new package, if I have to change the date range to find a deployment done several months ago, I lose the selected deployments from a more recent timeframe and can't select them all to combine neatly.
If we could see successful deployments by viewing the authorized Org in…
10 votes -
Selectively filter managed package metadata without excluding unpackaged components
Add the ability to filter in/out managed package elements from a comparison set at metadata type level. e.g. allow for the comparison of managed package objects and fields but exclude other managed package metadata types whilst allowing those types to be available for non-packaged constituents. More specifically for instance, exclude manage package page layouts and include managed package custom fields whilst including both unpackaged page layouts and custom fields in the comparison set.
The reason for this is to minimise the comparison set which can reach limits due to size whilst including all mandatory metadata elements for a deploy.
Using…
4 votes -
If we move Jira ticket to status "Deploy" -> get the code from the repo ->deploy to destination ORG
For example after Jira status "Deploy" is captured doing a comparison and deploying the changes will work.
2 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 -
Import list of metadata items into org comparison.
When running a comparison, a user should be able to import a list of metadata items based on an agreed format (likely API names). This list would allow the user to save effort from copy pasting api names if they track their changes in an external system. For example, we track changes in our release system within our Salesforce production org. Our manifest items are tracked such as "customobjectc.customfield__c" and have statuses such as new/updated/deleted so we have a historical references of our changes. Being able to import these changes while still having the ability to select…
2 votes -
view deployed components live
Show live the components deployed during the running of a CI/CD Job.
Like:
deploying class abc.......
deploying class xyz.......
deploying lightning Component abc.......5 votes -
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 -
This is related to webhooks feature in Gearset.
Currently webhooks allow to trigger external job like jenkins job using webhooks. However its doesn't give any information related to this job whether its been called or not or pass or fail.
Use case:
The Jenkins job which I am triggering through Gearset calls my regression tests which runs on Jenkins server. I want to see the information like the Jenkins job has been called successfully and test results like number of tests run, pass , failed etc.
Having this I can make sure the Webhook is working fine and know my test results in Gearset itself.
It would be…2 votes -
Support user record migration from production to sandbox or scratch orgs
New users are often created in the production org that need to be monitored and brought back to sandboxes as well. It would be great if the data deployment tool could support moving user records from prod to sandboxes or scratch orgs.
11 votes -
Metdata Optimization / CleanUp Analysis
A very good feature for metadata management tool like gearset will be an helper which allow to identify metadata not used or not properly configured.
For example this concurent have this feature : https://www.metazoa.com/snapshot-use-cases-org-cleanup-and-optimization/2 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 -
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 -
4 votes
-
Combine multiple daily monitoring results into a single deployment
If you want to deploy the differences of an org on a weekly basis, it would be a great option to take the monitoring results of the last 7 days into a single deployment.
Especially in huge orgs, where comparism takes 30 minutes time to show up, this would ease deployment pretty much.2 votes -
Make it easier to select all custom field translations for deployment
Right now if you want to select translations for certain custom fields, it is necessary to expand the sub-components for each field and select the translation. The second option is to go to the custom object and expand the sub-components in order to check translations which will include all the custom field translations for this object.
It would be helpful to get a way to select the translations for specific custom fields in the deployment.3 votes -
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 -
Static Code Analysis for JavaScript Components
It would be great if Gearset could run static code analysis on JavaScript as well as Apex when deploying Lightning Components.
7 votes -
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
- Don't see your idea?