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.
1301 results found
-
Modify the "Changed On" drop down filter groupings to round to the nearest day, rather than the exact time the change was made.
It would be helpful if in the "Changed On" dropdwn filter if it grouped it into days, rather than the exact time the change was made. Also, if there were preset groupings like "Today","Yesterday","Last 7 Days", etc.
5 votes -
Support multiple SFDX projects for a custom GIT repo
When comparing / deploying using a custom git repository, containing multiple SFDX projects, present the user with the ability to select which SFDX project to compare / deploy, either by package.xml or sfdx-project.json. Currently Gearset fails and reports multiple sfdx-project.json were found.
[
{
"UserReadableError": "This repository has 2 sfdx-project.json files: Gearset cannot determine which one to use",
"ErrorType": "ErrorFromSource"
}
]2 votes -
Distinguish between process builder and flow
If you do deployments of flows and processes from process builder, both of them are handeled as a flow. If you need to activate the flow or process manually in a production org, you need to guess if it was a flow that you have deployed or a process.
Please within the deployment report (and the comparism), distinguish between flows and processes.2 votes -
Add new connection ends in loop
When I add a new connection via choosing "Salesforce authentication", I need to enter the username. I click on "Authorize". Instead of a redirect to the Salesforce login screen, I see a blank page with a gearset spinner logo. But this screen takes hours and will not redirect. I'm using Firefox and the Org is a sandbox (sandbox is also selected)
1 vote -
Ability to change Formula Fields to other Field Types
Gearset doesn't help with one of the most common deployment headaches: changing a formula field to a non-formula field type. It's still a nightmare even with Gearset.
What would be awesome would be if you had a "Change Field Type Wizard" where we could say FormulaField1 needs to become TextField1 and it would do multiple deployments to accomplish the changeover:
- get components
- deploy temp field of new type AND update all existing components to reference the temp field instead of the formula field
- deploy delete of formula field
- deploy text field in place of the old…3 votes -
Ability to chose SFDX source format (force-app) compare or old style (src)
Add a checkbox to chose wheter we want a sfdx compare or an old one (in order to not let gearset chose for us)
1 vote -
call webhook with scheduled deployment
We would like Gearset to call a webhook when a scheduled deployment completes. The message to the webhook should pass a message with the org name, UTC datetime, the deployment friendly name, URL of Gearset deployment results and a status field with 'succeeded' or 'failed'
3 votes -
Add support for "ServiceCrew" and "ServiceCrewMember"
These two objects are part of the FSL package for Salesforce. Right now, when we do a compare between two orgs, no results with be shown.
1 vote -
While configuring a data deployment, allow save after selecting objects and fields
There's no opportunity to save the data deployment settings after selecting objects and fields, and this can be quite time consuming, so if the job fails due to auth or other issues, right now, this requires the user to start over, and re-select objects and fields.
1 vote -
Ability to upload Deployment Checklist instead of manually adding All components
For every release, we have at least 700-1500 or more components to be deployed and adding all those one by one into gearset is a lot of manual effort which might sometimes not be entirely accurate. It would be great if there is an option where we can upload an excel or csv with all the component names and gearset would just create the package for you. It would save a lot of time and effort and reduce manual errors.
12 votes -
Provide more detail in Monitoring notifications
Right now, the Monitoring job notifications (Slack especially) provide very little detail as to what actually changed.
Ideally, I'd be able to see right in the message (or in a threaded reply), the first X number of metadata changes made. If there are more than that, then providing a direct link to the detail page in Gearset would be great.
As of now, it simply just says "there were changes", with no detail or way to easily see the changes in Gearset...which is not terribly useful.
4 votes -
Allow Data Deployment to filter lookup fields on fetched data
Currently, when doing a data deployment Gearset will let you know of all the referenced objects from the object you selected. What it doesn't do is the opposite of that - let you know all the objects that reference your object with a lookup.
It'd be great if we could add a filter to utilize some data pulled in a fetch/query during data deployment.
ex. field (TeamMember.ProjectLookup_c in {returned Project results in query in previous step of data deployment).
7 votes -
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
- Don't see your idea?