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
-
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 -
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.
-
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 -
Object level filters for Monitoring
Object level filters for Monitoring
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
-
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.
-
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.
-
Some of the test monitorings "randomly" fail with WebResponseKnownError.
Is there a way to prevent that?
1 vote -
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! :)
-
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. :)
-
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 -
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.
-
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.
-
Allow users to choose when change monitoring and unit testing jobs run
The change & test automation is great, but we can't choose when these jobs run. The option to choose when to run jobs so they don't coincide with dev work would be a great addition.
10 votesThis has now been added to both change monitoring and testing jobs.
-
Add support for GitLab
Like the integration with GitHub, to compare and deploy from repos to our Salesforce orgs.
2 votesWe’re happy to say we’ve now launched GitLab support from within Gearset. You can compare and deploy straight from your GitLab repos to your Salesforce orgs.
-
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.
-
Add a test runner interface
Which would allow schedule full test runs and get an emailed report of all failures to stay ahead of an errant admin change blowing up a deployment, before you are validating a change set in your production environment.
1 voteThis is now live for all users under the “Schedule tests” tab in the app. You can also get notifications by email, SMS, Chatter and Slack.
- Don't see your idea?