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.
1243 results found
-
Allow owners to setup delegated org access of members
Without already having delegated access granted there is no way to rollback a deployment from another user. There should be a permission to override this.
2 votes -
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 -
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 -
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 -
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 -
Show JIRA issue summary when attaching a JIRA issue to a deployment
when Deploying metadata and linking it JIRA Issue it will be a good idea to have more Jira Issue fields visible not just the Jira Issue key(id).l would like to have Issue "Summary" field Visible
2 votes -
Support Email Template Folder metadata migration
Metadata API for EmailTemplateFolder does not accept wildcards so you have to know the name of the folder to be able to pull it down and migrate it. Currently (as of 2-16) the Gearset product cannot pull these.
Suggest that they add functionality to make a SOQL call to get all the folder names, at which point they should be able to pull them. Allowing for compare and deployment.
2 votes -
Filter Column Sub-Levels
If I filter a column, it does not apply those filters if I open the sub-levels of an item such as "Depends on" or "Used by". For instance, if I filter OUT under the "Difference Type" column "No Difference," when I search through those sub-levels, it should not show me items that are "No difference."
2 votes -
Add tool to send emails after deploying to specific targets
A project manager on my team expressed desire to receive reports when someone deploys to our production org. I would appreciate a tool that sends these emails only upon successful deployment to that specific org so that recipient's inbox is not flooded with every successful and failed deployment to every org.
2 votes -
Record/file level filters for Backup jobs
Allow Backup job filters to be configured for specific records/files rather than entire objects.
2 votes -
Meta Comparison Filter Based on User and/or Timeframe
It would be great if there was a way to create a metadata comparison filter, and not just filter with regard to metadata types, but also filter by which user made the change, or the timeframe when the change was made? For instance, it'd be great if I could create a filter based on changes I made within the past 30 days, or a specific timeframe. Filtering by metadata types takes very long for large orgs, even if I reduce the metadata types down to 1 or 2.
2 votes -
Production/Sandbox Backup job color
The backup job color (or a colored tag) should be introduced so you can clearly see which backup job is for Production and which is for a Sandbox.
At the moment they all look the same and you have to make sure you are clicking on the correct one, only by looking at the username to understand if it is a Production org or not.
This is confusing and risky
2 votes -
CI Deployment on a Schedule
We would love to schedule a deployment from GitHub source to a few sandboxes at the end of each 2-week sprint.
2 votes -
Allow the capability to deploy to multiple Salesforce organizations within one deployment
Currently you can only push to 1 Salesforce org, however, we manage multiple organizations and would like the capability to push the same package to multiple organizations
2 votes -
Gearset configuration as a Code (git or exportable)
Gearset configuration as a Code (git or exportable) so that there is a way to store it i.e. in Git and see how various jobs, cicd pipelines, monitoring and schedulers are configured which is an enterprise way to implement solutions nowadays (PaaS, IaaS etc..)
2 votes -
Add an Undo Action/Functionality in the Comparison UI
Add an Undo button to the comparison UI in case someone accidentally de-selects a component from the Selected Items tab. It would save time rather than having re-search for the component and lose your train of thought. You have this feature in Google Docs and sheets.
2 votes -
Rename the Name bar in compare and deploy to : Name (api)
Simple to implement, just a string rename...
Rename the Name bar in compare and deploy to : Name (api)
It would show clearly that the name displayed there is the API name, not the "label" name XD
Cheerio2 votes -
Add option to make picklist fields non-restricted before performing a data deployment
Similar to being able to disable validation before performing a data deployment it would be very useful if there was an option to automatically uncheck the "Restrict picklist to the values defined in the value set" option for some or all of the picklist fields in a deployment.
We have data that includes picklist values that are no longer active this causes errors on individual records as part of the load. Currently I have to pick through all the errors manually then uncheck the option for the corresponding picklists fields on the target org. Then after performing the deployment I…
2 votes -
sfdx repo deployment should be in subcomponents
Context: Compare and Deploy from Org to a Repo.
as i understand it, even if my repo is in SFDX format (Object subcomponents), Gearset still does the compare in the metadata format.
it reads the components from sfdx, combines into a .object form, and then applies the changes to the .object file and then decomposes again.this is causing unintentional changes to be part of our PR
2 votes
- Don't see your idea?