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.
1379 results found
-
Exclude OmniStudio generated LWCs for CI
Currently OmniStudio will generate LWCs for it's flexicards and OmniScripts.
We want to have CI syncing in to a repository, however we don't want to have these autogenerated LWCs in the repository. This is code that users won't be modifying themselves, isn't constructed to be read by a human, and will actually be controlled by the Vlocity elements that GearSet already supports.
Reviewing the metadata produced by omnistudio, it seems that all the LWCs produced have the runtimeNamespace tag in their meta.xml file set to 'omnistudio'. It would be ideal if we could filter out all LWCs with that tag/value…
2 votes -
Show "All" Different Items
Instead of a tab showing 'All Items', even items that are the same, maybe show a tab of All Different Items, which would show New, Deleted, and Changed in a single view without having to sift through the 'All Items' for these.
2 votes -
Allow users set their own default tab view when viewing the comparison between orgs
The recent change (March '22) to change the default tab when viewing a comparison from Changed Items to 'All Items' makes it more difficult to quickly see changes, because maybe there aren't any. The All Items list would also be extremely long if the org is particularly complex.
As such, I propose that you give users the ability to select their own default tab when the comparison page loads, so we can choose to always view 'New' or 'Changed' items.4 votes -
Additional text countries
I'd like to see a few extra countries added to the text messaging option on scheduled deployments. My team works with resources in different regions.
Brazil +55
India +91
Philippines +631 vote -
Add a Tab to manage Metadata Comparison Filter
Add a menu item or tab where we can
1. Share, delete, edit names of the custom Metadata Comparison Filters.
2. See the comparison history, who used the filter and when in team etc.4 votes -
Add the ability to report on validations and deployments via CI
Currently, it's not possible to see a report on when a validation or deployment started and ended for a given CI Job across multiple PR's. This will help understand how long on average validations or deployments are taking for a given environment.
1 vote -
Enforce each deployment to have a Jira issue in a specific status in order to be able to deploy.
As a gate-keep; to be able to deploy anything to production (or any other named environment), the associated Jira ticket must be in a pre-select status.
For example, the Jira ticket's status must be in "Ready for Deployment" to allow an end-user to deploy.
3 votes -
Add option to load missing dependeces only.
Example:
When I already selected metadata filter with many items, downloaded metadata, compared, checked, and clicked deploy then I am getting an error that some dependency is missing but it is metadata type that wasn't selected previously.Currently:
I need to click refresh comparison select additional metadata types and reload all metadata from both sandboxes. It is very time and resource consuming with big packages.As a solution:
I want to have the possibility to click a button and select on the metadata list only those that I want to add to the current package and only those should be…2 votes -
Add to draft deployment as you build
Ideally I'd be able to add metadata to a draft from within salesforce - via a chrome addon maybe?
1 vote -
I would like to be able to deploy directly from environment variables.
This feature would allow me to setup each sandbox environment after doing a refresh from production.
7 votes -
enable linking two separate gearset accounts when they are hooked to the org
I've been using Gearset for a few years. The Salesforce consultant I occasionally work with just started using Gearset with all their clients. So we both have a connection to my Salesforce org. It would be nice to see a combined view of deployments, validations, test runs, etc. made against my org - regardless of which Gearset account it was done from.
1 vote -
enable linking two separate gearset accounts when they are hooked to the org
I've been using Gearset for a few years. The Salesforce consultant I occasionally work with just started using Gearset with all their clients. So we both have a connection to my Salesforce org. It would be nice to see a combined view of deployments, validations, test runs, etc. made against my org - regardless of which Gearset account it was done from.
1 vote -
Field Dependencies for Reports
When deprecating a field and replacing it with a new one, we need to be able to see where they are used in all reports, including private folders, which the "Where is this used?" feature does not detail.
1 vote -
Manually Delete Metadata after CI job runs
We don't want the CI job to delete metadata, so we've unchecked that box. However, when a CI job runs that would have deleted data, we'd like to be able to select from the job history, review what would have been deleted and elect to deploy the deletion manually post CI run. We can re-run the comparision from Compare and Deploy, but having this action tracked within the CI job history would be more convenient, and would allow the history for the target org to be contained in the same thread.
2 votes -
Force a full production backup, and forbid its deletion
I was not able to buy this tool because to me it was a blocker that we have the right to delete the production backup.
I may agree that the we don't force for a full backup, but leaving the option to descope tables is equivalent as not backing up.
Force at least an initial configuration and allow only to add more scope to the backup, but never to reduce it or delete without contacting your support who should get an authorization from more than one person on the client side.If I'm an admin at salesforce, and an admin…
1 vote -
One-click Sandbox data deployment of all objects
I think a great feature would be for the tool to be able to copy all object data from one org to a sandbox, and if the amount of data is too large for the sandbox, allow the user to specify what objects to take sample data from - and how - i.e. take no data from a certain object,or take 5% of the latest created data, etc. It would be helpful to show the objects that have the most data.
1 vote -
Support SAML-based SSO and SCIM-based user provisioning
To improve security, user experience and reduce user administration time, SAML-based SSO and SAML JIT provisioning or SCIM-based provisioning would be fantastic.
3 votes -
Allow record data load from CSV file
While it is nice to deploy record data from org to org with Gearset, it would also be nice to be able to deploy data from a CSV file, with the ability to custom map the headers. Native Salesforce Dataloader has this capability, as well as many 3rd party tools out there. Please incorporate this capability into Gearset.
10 votes -
Users with access to same target org
2 users both have access to the same target org with different user accounts. User A creates a package and asks User B to deploy the package on their behalf. Unless User B has been delegated access to the same org they already have access to by User A's account then User B will be unable deploy the change as they receive the error
"To deploy you need deployment level permissions from the owner of the target"
Workaround to this security constraint was to download a copy of the package and deploy using Workbench.
2 votes -
Easier way to exclude multiple named items in the metadata filter.
In the metadata filter named items, I want to exclude 10 named items. Currently I have to use the "exclude" Object name button 10 times. I want to tick all the 10 named items, that currently allow to include, and click a button to turn them into "exclude" in the named items.
1 vote
- Don't see your idea?