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.
337 results found
-
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!
-
Configurable code coverage limts
The test automation nicely tracks code coverage and allows me to see when I'm getting close to 75%.
It would be good if Gearset could be configured to warn me when any of my orgs approach a limit that I control.
For example, we mandate 85% code coverage for our production org and I'd like to be notified if we start to dip below that.
2 votesThis feature has now been released.
When creating a job, you will be able to set a test threshold percentage. When your code coverage falls below this threshold, Gearset will notify you using your chosen notification settings.
Thanks for the suggestion. :)
-
Provide individual class code coverage statistics
Running tests displays overall org code coverage... it would be cool if you could provide individual class code coverage statistics as well, so we could get a good idea of what classes / triggers need attention
49 votesThis feature is now finished! Apex code coverage by class can be viewed in the details of a test job for all users with an Enterprise license.
-
Show more info on source control on comparison screen
Would be nice to see something like "SOURCE: reponame, branchname (username)" when comparing with a repository.
2 votes -
Display more information when a test method fails during deployment
When a test method fails during a deployment in SF, we get the message and the stack trace. This can be really useful in tracking down the source of the problem.
Gearset currently only gives the name of the method that failed, so extra info would be great. Ideally both the message and the stack trace.
1 voteThis has now been released. If a deployment fails due to a test failure then you’ll get the full stack trace in addition to the failure message. Let me know if there’s anything else you need from that part of the app
-
Add BitBucket Integration
Would be awesome to have the equivalent of GitHub and GitLab for BitBucket!
1 voteWe’ve now shipped Bitbucket support in Gearset.
-
Some of the test monitorings "randomly" fail with WebResponseKnownError.
Is there a way to prevent that?
1 vote -
7 votes
Failed deployments are now shown on the deployment history page: https://app.gearset.com/deployments/deployed
Failed validations are now shown on the validated packages page: https://app.gearset.com/deployments/validations
-
Deployment summary screen
On the Deployment summary screen, there's no indication on what are the source org and target org. Would be nice to be able to check before the actual deploy.
1 voteThis has now been released.
The pre-deployment summary screen now lists the source and target org so you can be totally sure what you’re about to deploy the changes to.
Thanks for the suggestion.
Jason.
-
Email notification for failed deployments
Getting an email when a deployment succeeds is nice, but it would be nice for failed deployments too. (Unless maybe I've missed an option for this?)
2 votesFailed deployments will now trigger an email notification, just like successful ones.
The email contains a summary of the failure information, and a link to the failure report where you can begin to debug and fix the errors.
Thanks for the suggestion! :)
-
Ability to store elements selected during a Comparison for later use
Use case, before a deployment I determine which components I want to deploy, validate the deployment ... but then want to complete the actual deployment at a future date from within Gearset (i.e. once we get sign-off from the client).
Yes, I am aware you can download the validated package. I want to (ideally) complete the actual deployment in Gearset.
2 votesHi,
We’ve just released our ‘draft deployment’ feature in the app which will allow you to do just this.
Here’s how it works:
- Run a comparison as usual. From the comparison results, click Save draft deployment
- Your object selections and the comparison will be saved to your Draft Deployment history
- You can then return to continue building this deployment from your history at a later date
- If you’ve invited other users into your team, you can also edit and collaborate on their Drafts to build a deployment package togetherHope that helps,
Jason. -
Option to run tests when deploying to dev or sandbox orgs
You run tests when deploying to production orgs, which is great, but sometimes I want to force tests to be run when deploying to sandboxes or dev orgs. Can you add in an option to run tests for these orgs?
1 voteThis has now been shipped. You can choose whether or not to run tests when clicking the deploy or validate buttons.
-
TLS 1.1 support
Salesforce are rolling out the requirement for org connections to use TLS 1.1 or above over summer 2016. Will Gearset support this?
1 voteGearset is now fully compatible with the TLS 1.1 and above requirements for all Salesforce orgs.
- Don't see your idea?