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
-
Test job triggered by CI job
Test jobs are only configured on time basis. When developer commit some changes and it will be deployed, but tests will be done on a time basis in 2 hours for example, so he should wait to know weather tests are passed or not. Or ask the release manager to run tests manually. So, this feature is must have improvement.
1 vote -
Support grouping of Manage Orgs page
Support the ability to group org credentials on the Manage Orgs page by a new Group Name attribute. In managing multiple clients with dozens of PRD and Sandbox orgs it would be extremely helpful to be able to group and filter related credentials by client. However, to expand this feature to support multiple use cases, providing a new Group Name attribute (text) which could contain any value would be fantastic!
Thanks for your consideration,
Mike1 vote -
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 -
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 -
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 -
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 -
View email templates that are part of a managed package folder in comparison
Hey guys,
I am not sure if this is an actual issue or not but I will ask the question to see if I am missing something :)
When comparing email templates, the compare will return both email templates and folders. I have noticed that in my case, email templates that are part of a managed folder do not return. We can see the folder and sync the folder settings, but no templates. If we move the templates to a non-managed folder we can see the templates. Has anybody encountered anything similar?
Thanks!
Richard
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 -
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 -
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 -
Page Layout Deletion Not Detected
When I remove a page layout from my Git repository (the file and the package.xml entry) and then do a comparison to an org that it still exists in, Gearset fails to detect a deletion. It doesn't even show up in the All objects tab. It happened to me yesterday and then I just reproduced it now.
2 votes -
Warn if a selected metadata type is not supported by selected API version
In the custom filters dialog, if you select a metadata type that is not supported by the API version, the compare and deploy currently just silently ignores that item, giving the impression that the compare has failed. e.g. selecting "Duplicate rule" with metadata version prior to 38.0.
It would be good for Gearset to provide a warning if a selected metadata type is not supported by the selected API version.
2 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 -
Show status in Chrome tab title
In Chrome, it is possible to display info even when viewing a different tab.
For example, I see this done with financial sites when they want to show the value of a stock ticker symbol.
2 votes -
Check for conflicts on CI
We have a scenario where CI would be useful, but there is a risk of it making destructive changes...
Orgs in involved are Prod, UAT, Dev.
Ideal development path would be Dev->UAT->Prod with each deployment using Gearset.
In the real world, admins make some changes directly in Prod. So, we also need to merge changes back from Prod->UAT to make sure that UAT is a realistic test environment.
It would be great if we could make a CI connection from Prod->UAT which automatically deploys non-destructive changes, and notifies us if a change cannot be sent to UAT for risk of…
2 votes -
The number of differences does not appear to the left of the Prev/Next buttons in XML view mode
However, the number of differences does appear when viewing the same Apex class in APEX view mode.
2 votes -
False positives in managed code
When I enable comparing managed packages (e.g. when I have added a field to a managed custom object), I get lots of false positives saying that there are differences in apex code.
On the source org, the code is show as "(hidden)"; on the target it is shown as empty. And Gearset lists this as a change.
Obviously, I know it's not a change, but it adds a lot of clutter to the comparison view.
3 votes -
Suggestion - make comparison highlight colors configurable
The background highlight colors for differences are much too light to be able to be seen clearly when viewing in APEX mode. Colors are much brighter in XML mode. Request - allowing these colors to be configurable. Thanks for the consideration.
1 vote -
Compare org monitoring from an arbitrary date to the current state of the org
In Monitor ORG's tab, we have a daily set of cached metadata that can be used to troubleshoot issues in an ORG. This is great that we have this data. What would be even better (if there is not a way to do it currently), is if we could take the metadata cache from the monitoring job, "x" days ago, and compare it to the current state of an ORG.
Maybe an ideal way to achieve this would be to select a cached version in the Compare Organizations screen. Alternatively, a button can be added in the Monitoring Job history…
3 votes -
A count of differences could be grouped by type
If the count of differences could be grouped by type/color that would be helpful.
Ex: 20 differences: 5 red, 7 green, 8 yellow. It gives a better sense of how drastic the differences between Source and Target are at first glance.3 votes
- Don't see your idea?