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.
1140 results found
-
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 -
2 votes
-
Clarify installation of managed packages and allow opt-out
It appears that if there are dependencies in the deployment that require a Managed Package to be installed/updated, that package is automatically installed/updated before the deployment takes place.
This is great, but it needs more clarity and control for the user.
It would be nice to know if Managed Packages are going to be installed as the result of a deployment, and if so, opt-in or opt-out of that process. It would be great if opting-out also displayed the related metadata with the dependency so those could be excluded as well.
This may also avert some errors where metadata needs…
1 vote -
Display org authorisation errors
When I link my Salesforce org with Gearset, I like to use OAuth as that provides the best security.
Whenever there is an error during the linking process, such as when:
- The app is blocked (OAUTHAPPBLOCKED)
- I press Deny on the OAuth consent screen
- The org has IP restrictions in place that prevents Gearset from completing the OAuth flow
Gearset returns to the Manage Orgs or Configure page without showing me what went wrong!
1 vote -
Filtering by user across the app
Filter deployment history & automated jobs to only show a specific team member's activity (e.g. mine). With large teams, the history pages can get too busy and makes it difficult to find the results I'm interested in.
1 vote -
Manage Orgs Re-authorization returns you to a default sorted list.
I refreshed a sandbox. I need to re-auth my orgs. I go to Manage Orgs, and sort by my friendly name. I click re-auth, and OAuth is successful and the app tells me I did a good job. But the page it returns me to is using a different sort then I left the page with. ie, it sorts the list by username again. Just extra button clicking I'd like to get rid of if possible. I have to re-auth orgs all the time.
1 vote -
Dependency Engine enhancement for Sharing Rules
Dependencies with sharing rules. Roles/Groups/Fields referenced in sharing rules may be helpful to add as "dependent" on as if they are not in the destination org you cannot deploy.
2 votes -
3 votes
-
allow multiple slack webhooks per scheduled monitor or test run.
I have multiple slack teams, I'd like the ability to hook up a monitor org, or a test run to send to multiple slack webhook urls.
Not super important, and I suppose I could get around it by scheduling a duplicate, but that just felt wasteful of everyone's API's. :)
1 vote -
Exportable metadata reports for orgs
Being able to export a summary of an org's metadata state for reference, prior to a deployment or as part of our reporting, would be great.
1 vote -
Identify different backup job types (full vs. incremental)
Today, it is not possible to identify the backup job type, so we cannot really distinguish between a full and an incremental backup. This would be helpful to get better visibility when a full backup job is/was running.
0 votes -
Filters
Edit "Existing Saved Filters" on an "Existing CI Job"
If using a saved filter on CI job, there is no easy to update an existing saved filter from the CI job directly.
Here is my current workflow:
Start a new compare and edit / save the filter from there, then going back to the CI job, refreshing filters and reselected the saved filtered.
If multiple CI jobs are setup it's easy to miss some jobs which are dependent on updated filter.
Alternative solution - Provide toggle to update all related CI jobs which use the filter.
0 votes -
Allow serial deployment instead of parallel
When executing a data deployment, an 'Unable to lock row' error can occur if multiple transactions try to lock the same record in Salesforce.
Because the batches are executed parallel, the chances of getting this error high, depending on the situation.
For example the master record in a master:detail relationship will always get locked when a DML is executed on the child record.
If two batches are executed at the same time and they both have at least 1 record that references the same parent, then a locking error will occur.0 votes
- Don't see your idea?