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.
1308 results found
-
More custom monitoring delays
It would be brilliant to be able to choose the days of a week your monitor script runs on so I don't have to deploy changes every single morning and could instead do once a week
1 vote -
to add an option to not to run unit tests validation in CI job in case there are no changes detected
2 votes -
Integration with Rocket Chat
Hello, I need rocket chat integration, in order to receive notifications in deployment group chat about deployment status.
Thank you.
1 vote -
Better error reporting when CI jobs fail.
Better error reporting when CI jobs fail. Many times I open a failed job and there are no errors reported.
7 votes -
Ability to clone deployments and include non-different (same) metadata items.
I would like to be able to Clone a deployment and include all of the metadata from the cloned package, even if there are no changes in the target org. This way I can incrementally build up a master package that includes all my metadata regardless of where I chose to deploy it.
1 vote -
Filter deployment and comparison reporting by user in the account page
Right now Gearset is showing Total Deployment Team wise . My suggestion is to Publish User Wise Count of Deployments with all Successful , Failed Deployments .
1 vote -
Show related reports as dependencies when deploying a Dashboard
When choosing to deploy a dashboard, It would be helpful if all of the reports that are used by that dashboard were shown as dependencies with the option to select them as part of the deployment
1 vote -
Make All Items show all items in the filter
On the comparison summary the All Items tab does not show items that don't exist in either org.
It is possible to add an item that does not exist in any org (perhaps by mistyping the name of a class/object/trigger/etc.) but the All Items tab does not show those items. It would be helpful if even items that don't exist in either of the comparison orgs were displayed in the All Items list and flagged as not existing. This will make debugging problems like mistyping names easier to diagnose.
I wasted an hour of my time and that of two…
1 vote -
Download metadata from monitoring job in SFDX format
Please add the opportunity to download the metadata from the monitoring and backup job in SFDX format.
1 vote -
to give an option to take a backup of Filter's data.
As an admin, I share my deployment filter with developers to add new item to filter. As many team members are working on the release , there is a possibility of jeopardizing the filter's data. I wanted to take a back up of the filter's items periodically. How can i do this?
1 vote -
Stop the reordering of XML when deploying to git
At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.
32 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 -
Allow Username/Password authentication option when selecting target/source orgs during cloning a deployment package
Currently, when cloning a deployment package or re-deploying a package to a new target, it only works with OAuth authenticated orgs. It would be nice to have more of my available saved orgs to be a target/source when cloning a deployment. I am not able to authenticate a target or source using a My Domain or Username/Password with this method.
1 vote -
Improve CI validations jobs - allow incremental comparisons with Github Pull Request/Push Validations
Currently, the only way to validate a branch, push, or pull request is to essentially have gearset pull all metadata from the repository and the org.
This can result in a long wait time for validation. It'd be great if we could have quicker turnaround for users to get feedback after a push/pull request.
Since github/provider of choice would have the exact metadata that changed in the push/pull request, it'd be helpful to only have gearset pull the metadata that actually changed to limit how much time is spent simply pulling all metadata to make the comparison.
2 votes -
Allow download of the zip package for failed CI jobs
Download the Gearset constructed package from CI job history when the CI job failed
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 -
Create Change set without comparison
Allow user to directly create a change set without doing the comparison. If user has a list of items that needs to be migrated then allow the user to add items and skip comparison step.
25 votes -
Provide controls around who can create/manage Salesforce Connections
I have a team of multiple admins that use GearSet and I want to fully control who can deploy where. I can set this up with security today in GearSet by what kind of access I grant. However a user can create their own connection using their credentials and get around the shared connections I have established. I would like the ability to disable a users ability to create new connections which would then only allow them to use pre-existing connections that I have established appropriate security for.
1 vote -
Include Apex classes imported into LWC
Ensure that Apex Classes imported in LWC javascript files are included in dependencies.
2 votes -
Provide integration with WebexTeams
We moved from Slack to WebexTeams and have lost the ability to post deployment notifications from Gearset. Here's an article about Webex Bots: https://developer.webex.com/docs/bots.
3 votes
- Don't see your idea?