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.
347 results found
-
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.
-
allow meta data compare to be optional for large orgs
When preparing any deploy in Gearset, it requires a full meta data pull which can take 10-15 min (and then timeout) to do any deploy. This is extremely challenging when we're just looking to deploy a new custom field or workflow.
It'd be ideal to add an option for not doing a full org compare/diff and instead allowing for selecting the meta data components you need to migrate.
2 votesYou can select specific metadata object types to include in your comparisons from the “Manage custom filters” dropdown underneath the “Compare now” button in the app. This will only download the selected metadata types, and speed up your comparisons.
-
Show which tests have been run
In the post-deployment summary, rather than just list the numbers, list the actual tests that have run.
2 votes -
Add support for cloning a deployment
Having already made or attempted a deployment, it'd be nice to be able to deploy the same set of resources to another org (essentially creating a deployment package).
5 votesYou can now clone an inbound deployment package by selecting “Clone deployment” from the deployment history tab.
-
Offer a hosted version of Gearset Deploy
As well as providing an installer, it would offer greater flexibility if you could also provide a hosted version of Gearset Deploy.
16 votesI’m happy to announce that we’ve now launched a hosted version of Gearset Deploy.
Simply visit the site (https://gearset.com) to try it out. If you have any feedback about the hosted version, please feel free to leave feedback or email the team directly at team@gearset.com
-
Stay logged in / save comparisons
At the moment I need to login every time I want to do a comparison, so a stay-logged-in feature would be great, as would the ability to save a comparison and re-run it rather than need to customise it each time.
1 voteHi Jonny,
I’m going to mark this as completed, although it’s more of a completed two out of three requests.
We’ve added a comparison history feature so that you can easily access the results of any comparisons you’ve carried out between two Salesforce orgs.
Additionally, we’ve improved the customized comparison functionality by adding the ability to save customized comparisons and improved access for selecting them on the main UI which will be a big time saver for you.
We haven’t added the stay logged in feature and we can future that.
-
Add an OAuth feature for connecting to your orgs
As well as the username/password option on the credentials page - add an OAuth option to enable connecting to the source and target orgs.
13 votes -
Provide support for deployment and object dependencies
Gearset Deploy should provide a way to show any object dependencies before a deployment is due to take place.
10 votesDependencies are now available, and you’ll be warned when you try to deploy an object without its dependencies.
-
Persist a customized comparison config when starting a new comparison
If I choose to compare specific types using the Customize Comparison feature - Gearset Deploy should remember those choice(s) when I start the subsequent comparison(s).
4 votesYou can create and save custom comparison filters from the dropdown underneath the “Compare now” button on in the app.
-
Improve the functionality of the code diff viewer
The diff viewer could potentially have several enhancements:
- add indicators as to where the differences are in the overall file. This would give you visual feedback and let you scroll to a specific part of the document. They could also be clickable to jump specifically to the diff(s).
- Collapse by default lines that are the same to reduce the need to scroll and focus more easily on the diffs.
- Potentially offer the ability to switch between the current side-by-side view to something like the format in GitHub with differences grouped vertically.
- Add the ability to undock the diff viewer from…
7 votesWe’ve made many improvements to the diff viewer over the past year. These include, highlighting the code diff, auto scrolling to changes, resizeable diff viewer, grouping complex objects (e.g. Profiles) into logical groups for easier navigation, and Picklist rendering. Shortly we’ll be adding image rendering too. If you’d like to see any other specific additions, please submit a new idea so we can keep you up to date with our progress.
-
Provide more feedback about progress when comparing/deploying
It would be an improvement if additional user feedback could be displayed about the progress of the comparison or deployment stages. Something showing the percentage of progress or an estimated time to complete if possible.
2 votesWe now show you which batches are being downloaded.
- Don't see your idea?