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.
1306 results found
-
Add additional deployed packages
When combining packages for a deployment to a new source, it would be helpful if I could add additional packages to a comparison. There are times when I realize a package or two may have been missed in the original combination, and when reviewing the missing components, I realize a missed another deployed package. Without the ability to add additional packages to the comparison, I must start the combination of packages all over again.
1 vote -
Select All Option in Deployment history
It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.
2 votesThis is now possible as long as a filter is applied to the deployment history page.
-
Send email alert when monitoring job fails
It would be helpful if Gearset would notify the user when connection problems cause a monitoring job to fail.
For example, if the error "Error while getting access token due to expired access" occurs, Gearset could send an email to the author of the monitoring job informing them of the problem.
3 votes -
Add option to provide exact time in case automatic deployment
We need to set exact time for automatic deployment. We need this option for example for night releases for specific client. This is important for international clients that works in different time zones
2 votes -
Add the ability to create some custom reporting against metadata change monitoring
I would like the ability to report on changes for an org over a time period grouped by metadata type or user. Filters would be by data, user, metadata type, change type. Would like to export or email the report too.
1 vote -
Ability to recreate a reusable list or group for Deployment notifications
Every week we have a larger sized scheduled deployment for logic updates that runs after business hours. There's usually the same 2-6 people (often increasing) that want to receive an email and/or text message when the deployment succeeds. Whoever schedules the deployment has to add each one manually every time, and it would be nice to have a way to send notifications to a predefined list or group of email addresses and/or phone numbers.
It usually has to be the person that schedules the deployment, because if someone goes back to add their own email or phone to an already…
5 votes -
Add or ignore parts of XML after the comparison to ignore other users changes
If there are multiple users making changing the metadata in Salesforce and when one has to deploy their changes, it is not possible to pick the changes that are specific to one person, For this we have to go to VS code and use git patch mode to add only the necessary changes for a specific user. If we have an option to edit the xml after the comparision and pick only necessary pieces and deploy it to next org will save time and also switching between multiple orgs. Currently the comparison editor is read only mode.
7 votes -
Make org-org and org-VCS compare differences work the same
There is no end to confusion on the part of the devops user when Gearset displays differences "differently" when comparison is org-org vs. org-VCS
Gearset should apply a consistent principle - to see a Profile subcomponent, the compare filter should include both sides of the subcomponent (e.g. Profile + ApexClass to see ApexClassPermissions; Profile + Layout to see layoutAssignments; etc.)
If both sides of the subcomponent are not included in the filter, then there's no difference to show.
Note that these use cases must also be supported:
Profile deleted in org; org->VCS compare should delete .profile file…
2 votes -
When an Installed Package is installed via GS permission sets with View/Edit All Data system permission don't automatically get updated
When an Installed Package is installed via GS, permission sets with View/Edit All Data system permission don't automatically get updated for the new objects in the package like they do during a manual install. We then have to update the PS via deployment or manually or future deployments will fail with "Read All permission is required for [sObject]". I would think it would be fairly safe to allow GS to automatically add the appropriate object permissions to the perm set in the target org since Salesforce requires that all objects have, at minimum, the same level of access as the…
1 vote -
Export Validated Packages
Ability to Export Validated Packages from Grid, like Deployment History.
1 vote -
Ability for Enterprise User with Role "Owner" to Delete Validated Deployment by Other User
This feature would allow Enterprise user with Role"Owner" to Delete Validated Deployment by Other Users. The reason for doing this is that there could be packages created in error and this would allow release managers who are typically owners to cleanup.
1 vote -
Deploy first fields where <trackHistory> was changed from true to false.
Deploy first fields where <trackHistory> was changed from true to false.
I am currently deploying fields changes and getting error that too many fields are tracked because fields with true ale deployed first.2 votes -
Make metadata filters easier to use when you want to "include all except X,Y"
For CI jobs, it is not uncommon that you want to include all elements of a given custom metadata type except specific elements
Today, you need to have two entries - an include all (".*") expression and an exclude expression. For users who are not regex savvy, this is too complicated.
We should have "All", "Named", and "All except Named" at the top level so simple check boxes can be used.
This is particularly useful for CI jobs (whose purpose is to sync VCS w/ org) - you want to sync most everything except a few items - like Sites…
1 vote -
Add a deployed components count to the Deployment History table
We'd like the ability to view the number of changes that were deployed from the Deployment History table view so that we can quickly scan the list of recent deployments and identify certain deployments using that additional information.
1 vote -
The ability to deploy only certain fields in a record type and not all fields
If we want to promote a change to a single field in a record type, we're unable to because the file is pushed in it's entirety. We'd like the ability to view from list of available changes in a record type by field and select just the changes to the fields we want to promote.
3 votes -
Option to have SCA results for last commit or Period, Instead of SCA for complete file
Hi All,
We are looking for a SCA feature so that instead of showing all the errors and warning in the whole file while doing compare or deploy, It Should only show the SCA errors and warning for the last commit or for commits during an specific time interval.
For Example I have an existing Apex class which is having 1000 lines of code and say 100 errors are there as per GS SCA analysis. Now let’s assume I am working on that file for my current sprint and I am adding another 100 lines of code in that class.…
2 votes -
Show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB
I suggest you have functionality to show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB
2 votes -
Expose Salesforce Validation Errors within Github PR
Currently when a PR Validation fails (Deploy CI Job with Validate Target setting turned on), the user can click the Gearset "Details" link to go into Gearset to see the exact error.
Many of our devs use VS Code and Github for their daily work and only rely on Gearset for the CI job. Having them jump into Gearset just to see the error is time consuming and not very intuitive for them. Sure we can find the same errors within the target org of the CI, but at that point the list of validations is large and it's hard…
9 votes -
resize column widths on "deployment history" page (no truncated values)
On the deployment history page, the column widths are fixed. If you have a value in the "friendly name" column that's over a certain character count, it gets truncated automatically. there is a tool tip to see the full value by hovering, but if you use consistent naming standards for naming deployment packages, this can result in having to hover over many package (i.e. rows) to find the one you want.
if making the column width customizable isn't possible, then making the "friendly name" column character limit longer would be a good start!
3 votes -
Create a Data Deployment Template for migrating Territory Management (1.0 & 2.0)
I would like to see a gearset defined template for Territory Management in Salesforce. I am definitely in need of this functionality as it seems to be a post deployment step once you deployed all Territory Management metadata.
in ETM 2.0 for example, after deploying the related metadata you need to deploy all related records for UserTerritory2Association Object, this contains who are the users assigned to a territory.
Not a big template but can be a good thing to have as a preset.
3 votes
- Don't see your idea?