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.
369 results found
-
Allow teams to share custom filters
Allow those filters we can save to be shared amongst our team!
7 votesCustom filters are now automatically shared with other members of the team and can be selected from the saved filter drop down when setting up a comparison.
Blog post on usage: https://gearset.com/blog/shared-team-comparison-filters
-
Allow GitHub to be a Target, not just a Source!
Let us move changes to GitHub!
5 votesWe’ve now shipped the ability to choose GitHub, Bitbucket and GitLab as the target for deployment.
Simply pick the Source Control option on the target when configuring the comparison.
-
Display deployment history in a list
Currently viewing the deployment history requires opening a pdf. If going back in time the only way to find a specific item that was deployed is to open one pdf at a time and look for the change.
It would be great if clicking on a past deploy would show items deployed in a list form on the page itself. This would make finding a past change easier.
2 votes -
It isn't obvious that you can sort by the "selected" column
It isn't obvious that you can sort which items you have selected while inside the "Changed", "Deleted", and "All" tabs of a comparison.
It would be better if you followed common web patterns like those found in GMail with the
...symbol in the column.See attached screenshot for example
1 voteAs you identified, you can sort by selected objects by clicking the header to the right of the select all checkbox.
We’ll have a look to see if we can make this a bit easier to discover.
Thanks,
Jason. -
Allow me to exclude metadata.
I have certain metadata which is broken or dangerous to migrate from a dev org, I'd like to exclude it from this and subsequent releases. If I could 'right click' and ignore it that would be good.
20 votes -
HTML email template - require Letterhead
Currently when deploying an HTML email template I get an error. This is due to the Letterhead not being present at the target. If I select the letterhead in the source and deploy it along with the HTML email template the deployment succeeds.
It would be nice if Gearset could see this dependency for the Letterhead and prompt to include it as part of the deploy
1 vote -
Use Draft deployment name as the Friendly name...
Would it be possible to have the draft deployment name, default to the friendly name under deployment history?
3 votes -
Deploy detected changes to other orgs
Being able to detect and roll back changes to orgs through the change monitoring is cool, but what I'd really like is to deploy detected changes to other orgs.
For example, if we detect a new configuration change to Production, being able to clone that change back down into our Sandboxes directly from the monitoring snapshot would be a real time saver. Or if someone deleted something in Production, being able to make that destructive change down into the Sandbox.
It would help us remove the step of running the comparison and pushing the changes after seeing a monitoring job…
14 votesThis is now shipped and live in the app! We’ve written a small blog post that walks through the feature and the use case.
https://gearset.com/blog/migrating-quick-fixes-in-salesforce-to-source-control
-
"Run now" button for test automation
Adding the ability to kick off a test job on demand, rather than the daily or configurable frequency
9 votes -
Deploy from change monitoring result
It would be great to be able to deploy changes detected in a specific change monitor result from the report history. Either to roll them back if they are unwanted, or deploy them to other orgs to replicate them into dev boxes.
0 votesWe think there are two parts to this request.
We’ve now added the ability to roll back changes from a change monitor result – you can selectively remove any changes made to that org on a daily basis by comparing from a snapshot to live state.
We’re now working on adding support to clone a detected change and deploy it to other orgs. This would let you push changes made in Prod down to a Sandbox, for example.
The second part of this is contained in another ticket, so we’re marking this one as completed.
-
Deploy to source control
It would be great to be able to deploy changes to my source control system, as well as from them, from the hosted app.
0 votes -
Track deployment validation errors more easily
When a deployment or validation fails, Gearset helpfully provides a list of the failure reasons. But when I go back to the comparison to make the changes, it's easy to lose track of what needs to be fixed. Adding the ability to export or save the warnings so I can easily work through then as a reference list.
0 votesYou can now export deployment failures as a CSV file from the validation or deployment failure screens. The CSV show the objects and their associated errors.
We may add additional functionality to this over the coming months to expand on how we track and display errors to make the process even easier.
-
Continuous integration
Ability to set up a scheduled sync between two orgs at a regular interval, with reporting and history tracking.
0 votesCi is now released. Enterprise users, and new users on a trial can now set up CI jobs to automate their release management. See this blog post for more information: https://gearset.com/blog/salesforce-continuous-integration-in-gearset
-
Allow multi-selection of items with CTRL or SHIFT
It would be great to be able to select multiple items in a comparison using crtl or shift click, rather than checking the boxes one by one
8 votesReleased on 10th of Aug 2022
-
Please don't try and deploy 'changed' Process builder processes.
Process Builder Flow versions appear as separate elements for deployment. Unfortunately you can't re-deploy an existing Flow, it won't let you change it, so Gearset shouldn't suggest that as an option.
2 votesThe latest release of Gearset includes additional dependency analyzers which should automatically find and resolve the issues around deploying flows. This includes detection of active flows, flow definitions, and deletions of flow definitions.
My colleague Matt has emailed you with a more detailed summary of what’s changed.
Jason.
-
Warn about unsaved changes to my draft deployment
The Draft Deployment feature (https://gearset.com/blog/collaborate-with-draft-deployments-from-gearset) allows me to quickly build up a deployment, but I sometimes press Next to kick off the deployment without saving the current state of things I have selected.
If the deployment fails, I sometimes can't get back and need to go to an earlier version of my draft.
It would be great if you could prompt me to save when leaving the results screen so I don't forget.
6 votesApologies – this feature got pushed back a bit! We’ve now shipped version one, with a couple of small usability tweaks coming soon.
As always, thanks for the suggestion. Let us know if it doesn’t work as expected, either here or in the in-app chat.
-
Naming Org Pairs
I'd like to be able to name 'Pairs' of orgs so I don't have to re-select them, like 'DEV to UAT' or 'HOTFIX to Production'
38 votesReleased on 12/10/2020
-
Support v37 API Metadata Items
I'm unable to deploy metadata items that were introduced in v37 of the API.
1 voteWe’ve now migrated to v37 of the API.
-
Sort on column headings in Manage Orgs page
Ability to sort on the column headings in the Manage Orgs page.
0 votesUpdate on 19th July: this is now live
Thanks for suggesting this, it should make the Manage Orgs easier to use.
This work has been completed on our preview environment and is going through our testing cycle.
ETA is to release this on 18th or 19th of July.
Thanks,
Kevin -
Desktop Comparison - "Referesion Comparison" does not clear modal background
Using the Gearset Deploy desktop application (specifically for on-disk comparison):
1) Compare environments
2) Wait for loading until comparison view loads
3) In comparison view click "Refresh Comparison"
4) Click "Refresh" in modalResult:
Grey background for the modal remains. No interface elements are clickable.
Note: Tabbing to elements behind the window shade still works.1 voteThe fix for this has now been released. Thanks for flagging it up!
- Don't see your idea?