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.
244 results found
-
Use exact filters of Automated Job
Currently automated CI job filters are unique to that job and not available as a filter for manual jobs.
Ability to use the exact current job filter as a filter outside of the CI job.
Ability to to clone the CI Job filter into a new named filter.1 vote -
Support package.xml filtering when using Git comparison with a SFDX folder structure
When using a git repo with a SFDX folder structure + package/xml (in the /manifest folder) gearset dos not take into account elements in the package.xml when checking the option (filter with package.xml)
39 votes -
Add a tab for Items that the Items I Selected Depend On
It would be so cool if there could be a tab that shows all the items that my selected items depend on. It would be much easier to review / select them then the way I do it now, which is expanding each item in the Selected Items tab to check for things I need to add.
Thanks!
5 votes -
Move the configured regex filters to the top of the scrollable pane (currently at bottom) of
Move the regexes to the top of the pane so one can see they exist and not have to guess that they exist at the bottom of the pane.
Note the example, selects all custom objects - this is useful for ISVs
example: For custom object, there are 100+ entries for standard and custom objects. If you add a regex, it appears at the bottom of the scrollable pane, after all the enumerated objectnames. Coming back into a custom filter, it is not obvious that you had even created a regex as you would have to know to scroll to…
1 vote -
create a compare/deploy function for data similar to metadata
having something like new/different/deleted for data (so we can compare, say, products vs new product options or features) like we do for metadata
5 votes -
expand the export comparison option to include the details changed between the objects and not just the object name time and type
expand the export comparison option to include the details changed between the objects and not just the object name time and type
1 vote -
Include the local file name on all the results screens
When you choose a local file to use as compare, on every subsequent screen the only title you see is: "On-disk repository". It would be helpful to include the name of the file.
1 vote -
Include the local file name on all the results screens
When you choose a local file to use as compare, on every subsequent screen the only title you see is: "On-disk repository". It would be helpful to include the name of the file.
1 vote -
Provide ordering for metadata elements when committing to version control
When metadata is retrieved from Salesforce the order of child nodes is not guaranteed and results in false-positive changes when committing to version control. Usually this will be something simple like workflow actions/criteria appearing out-of-order which can be compared manually. However, recently we've noticed entire profiles being committed with every permissions element out-of-order, resulting in a change set with ~20k lines where the actual change is impossible to visualize.
Gearset should provide a feature to 'order' child XML elements alphabetically by name in order to provide consistent commits to version control and eliminate false-positives.
10 votes -
Allow Scheduling of Comparison and Export Results via Email
Our use case is to schedule the comparison of two sources (Salesforce orgs) which are both "dev" environments, on a daily basis, yet receive the comparison results as an email attachment. The format of the export file within the comparison itself is what we'd need. This would save time & clicks by not having to log into the app and dig into the comparison job to manually extract the csv file.
4 votes -
Add support for "ServiceCrew" and "ServiceCrewMember"
These two objects are part of the FSL package for Salesforce. Right now, when we do a compare between two orgs, no results with be shown.
1 vote -
Show related reports as dependencies when deploying a Dashboard
When choosing to deploy a dashboard, It would be helpful if all of the reports that are used by that dashboard were shown as dependencies with the option to select them as part of the deployment
1 vote -
Make All Items show all items in the filter
On the comparison summary the All Items tab does not show items that don't exist in either org.
It is possible to add an item that does not exist in any org (perhaps by mistyping the name of a class/object/trigger/etc.) but the All Items tab does not show those items. It would be helpful if even items that don't exist in either of the comparison orgs were displayed in the All Items list and flagged as not existing. This will make debugging problems like mistyping names easier to diagnose.
I wasted an hour of my time and that of two…
1 vote -
Improve CI validations jobs - allow incremental comparisons with Github Pull Request/Push Validations
Currently, the only way to validate a branch, push, or pull request is to essentially have gearset pull all metadata from the repository and the org.
This can result in a long wait time for validation. It'd be great if we could have quicker turnaround for users to get feedback after a push/pull request.
Since github/provider of choice would have the exact metadata that changed in the push/pull request, it'd be helpful to only have gearset pull the metadata that actually changed to limit how much time is spent simply pulling all metadata to make the comparison.
2 votes -
Categorize Meta Data Filters
Allow the custom meta data filters to be categorize or put in folders. You could organize your filters by customer, deployment type, etc..
4 votes -
Ability to Compare metadata filters
When we have too many metadata filters, it is getting hard to keep track of them and figure out the similarities between them. It would be great to have an option to compare custom metadata filters.
2 votes -
Separate the Custom Settings <object> Permissions and Metadata Type permissions from the Profile or Permission set
When promoting Custom Objects and their security, we have to look at Custom Object Permissions (after loading the respective Profiles and Permission Sets in addition to the Custom Objects). We should follow a similar model for Custom Settings and Custom Metadata Types. The reason is that, if they remain part of the Profile or Permission Set, then I have to make sure that the Profile or Permission set exactly matches what I want in the target environment - I can't have any extra Custom Settings or Metadata Types that don't exist in the target environment yet or the promotion will…
1 vote -
add a wrning
when adding filters in the manage custom filters section can you a check to see if the contents look like regex, and the type selected is "object name" can you pop up a warning aong the lines of "Are you sure you don't want a regex filter?"
1 vote -
Namespace Mapping for Managed Packages
We are an ISV partner with a managed package we sell to lots of customers. That means our package is namespaced. However with a distributed development team and multiple dev orgs, all source code is not namespaced, and is maintained in source control (github) without namespaces. Only upon unit test and promotion to the package org, does the namespace get added. This results in two basic problems (and others). 1) comparisons between unit test and package result in almost everything being flagged as "changed" due to the namespace, and 2) all aura components are always flagged as "new" when they…
7 votes -
1 vote
- Don't see your idea?