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.
1152 results found
-
Integrate with Jenkins
Build a Jenkins Plugin to integrate with Gearset that would allow triggering CI jobs and/or deployments.
6 votes -
Allow a deployment team to update the same draft deployment at the same time or warn the end user of a draft in use by another user
When a dev team work on a shared deployment, it would be nice to work on the same deployment draft, at the same time. At a bare minimum, it would be good to be warned that someone is updating the draft at the same time as you.
1 vote -
Ability to copy Territory models from one org to another
It would be great to be able to copy Territory models from one org to another, as per this request in the SFDC Community...
https://success.salesforce.com/ideaView?id=08730000000DgemAAC29 votes -
Provide an API for querying deployment info
Please provide an API for querying deployment info such as friendly names, components, deployment notes, etc...
9 votes -
Filter standard vs custom objects
We sell a managed package and will never include standard objects in a comparison, and absolutely not in source control. When I'm running a compare against source control to check for changes, it will show all of the standard objects as "custom objects" which is not correct. I should have a way to filter out standard objects from the comparison.
1 vote -
Add an auto-save feature while building deployment packages
As Gearset is run through a web browser, if the browser happens to freeze while a package is being built, you don't have the opportunity to save it as a Draft Deployment. An auto-save feature would allow someone to pick up where they left off, or when the last auto-save was done, without having to start from scratch.
49 votes -
download the zip package at an earlier stage before analysis has taken place
Download the zip package at an earlier stage before the analysis has taken place.
In big Orgs with multiple teams working the analysis page takes sometimes to load so it would be a great addition if we can download the zip package file and modify it.1 vote -
Automatically revert PR in GitHub CI Jobs
When a CI job fails, the bad code remains in the GitHub repo. I'd like to see a way to revert the commit/PR that caused that failure so that any CI jobs for new, unrelated, commits/PRs won't fail while the developer is working to resolve the issue.
10 votes -
8 votes
-
Would like the ability to print the current comparison for selected objects before deploying
I would like the ability to print the current comparison for selected objects before deploying to use for documentation purposes.
1 vote -
Improve comparison performance
If there is one thing that is :-( about Gearset is that for moderate size orgs (a few thousand objects), the default 64 comparison takes too long.
You want to initiate a deployment from source to target and, for whatever reason, you want to make sure you didn't miss anything that needs to be deployed
So, to be safe, you initiate the 64 default comparison.
And you wait (downloading, comparison). This can take several minutes. You go on to other tasks and your zeal to get the deployment done went off onto other things as the comparison time is too…
4 votes -
Avoid going to Setup | Deployment status on "validate deployment don't run any tests"
If you are deploying to PROD and
a) You have Apex classes in your deployment
b) You choose Validate Deployment - Don't run any testsThe Validation will fail and Gearset will tell you to check the target org Setup | Deployment Status where as suggested, the most likely cause is test coverage failures.
This is in fact true but it seems that Gearset could warn you before acting on a PROD deployment with non-test apex classes and 'don't run any tests' that this will be guaranteed to occur and give you a chance to reconsider your choice before wasting…
1 vote -
Access to Critical Updates
We use Gearset as our primary utility for managing various client orgs include Production and Sandboxes for Testing and Release Management. It would be great if there was also a way to access, review and potentially enable/disable any Critical Updates in any org from Gearset.
However, I do understand that Critical Updates may not currently be accessible from the metadata API.
Just a thought,
Mike1 vote -
Provide a way to deploy push topics
We have a push topic that we use but there is currently no easy way to deploy changes between orgs. Would it be possible to do this via Gearset?
2 votes -
Field Tracking Analyzer message is misleading
If source org includes a new custom field with field history tracking enabled TRUE, the deployment analyzer reports the following when deploying to target org:
'Fields with history tracking enabled cannot be deployed before it is enabled on the object. You should remove these history tracking changes from the deployment'
Specific use case was object OrderItem
Analyzer can clearly detect if field history is enabled on target org object (which it was) - message is spurious.
Analyzer can arguably detect that target org's limit (20) will be exceeded by the deployment of the selected custom fields (which could add/remove field…
1 vote -
Option to validate / deploy only running test classes in deployment set
When deploying, there's a pain point when we want to specify tests to run. It would be nice to have an option to only run test classes that are included in the deployment. Automatically identifying which test classes are in the deployment package should be fairly straight forward:
grep -ri @IsTest ./src/classes
11 votes -
Have a timer on the compare page to indicate how long the compare is taking
Sometimes a compare can take us 30-45 minutes depending on the complexity of the org. I would like to see a running timer on this page of how long the compare is taking. I don't expect it to say how long is left, just how long it has taken so far. This will help to highlight if any abnormalities are happening, ie. if it's taking a very long time and is only at the Downloading phase for example.
4 votes -
Display which apex triggers have low code coverage if a deployment fails
It would be great if Gearset can surface which Apex trigger has 0% code coverage when a deployment fails.
9 votes -
Enhanced Comparison filter - filter by difference count
My use-case would somewhat be handled by separating code and xml differences, but I would like to be able to filter on difference count (or at least, easily see / sort by diff count).
For example: We are updating the API version on all of our classes and triggers (about 279 files this go around) and I want to make sure that the API update is the only diff when doing a deployment. Or to be worded differently: only deploy files where the only difference is the API version.
1 vote -
Support customer S3 buckets for storage
Allowing customers to specify their own S3 buckets for storage could be beneficial for the product. This would give the customer enhanced security and control over their data.
1 vote
- Don't see your idea?