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.
1142 results found
-
Sort Validation Only CI Jobs
In the CI Job page, you can sort the top-level jobs by different columns (Job Name, Source, Target, etc...) but you can't sort the actual instances of that job.
We can get up to 30 PRs that are all being validated, and it would be nice to be able to sort them in some controllable way. It seems to rearrange them in whatever way it feels.1 vote -
Be Able to deploy Portal Sharing Settings and Organisation Wider Default Sharing Settings at the same time
For example if attempting to deploy
OWD permission Read -> Private, and Portal Sharing Set None -> Read. Gearset will fail validation due to SF complaining that Portal Sharing Settings cannot grant Read permission, since OWD is already giving that access.
Though what SF sees is that Portal Sharing Set is trying to give Read when it already has that access.Therefore, if I want to make the deployment then I would have to do in 2 steps.
1 vote -
Allow Data Deployment to handle more complex structures
Currently, user is able to select Obj A, Obj B that references Obj A, Obj C that references Obj B. And, in the next step of data deployment it allows user to select Objects where Obj A, B or C, and objects references by those objects.
If we ignore above example, I want to be able to select: objA(id), objB(id, objA), objC(id, objB, objD), objD(Id), objE(Id, objD). Where the first object I select and everything else is filtered on is objA.
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 -
Activity Task Event field level security validation in Profile
Hi Gearset Team,
I would like to have a metadata validation for profile field level security involving Activity, Task, Event object as they are related to each other in Salesforce.
For example:
If we do a retrieve for Activity, Task, Event object along with profile. In the profile metadata it would specify this:
<fieldPermissions>
<editable>true</editable>
<field>Task.FieldX__c</field>
<readable>true</readable>
</fieldPermissions>However, if there were to be a mistake in the profile metadata and we commit them in version control it is detected as a 'new item' in Compare and Deploy
<fieldPermissions>
<editable>true</editable>
<field>Activity.FieldX__c</field>
<readable>true</readable>
</fieldPermissions>When we select this new changes and…
1 vote -
Ignore Business Owner changes between Sandboxes
This was marked as "Completed" in https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39507649-resolve-data-owner-user-metadata-from-difference
But really the issue remains.
When "Business owner" is populated in a field, it will show as "different" since the XML is showing username, which is different between sandboxes.
This make trying to do comparisons to find differences very challenging.
3 votes -
comparison between 3 or more ORGs
i would like to see in a future update about comparing 3 or more Orgs to possibly fine tune checks between production, and multiple sandboxes to make sure everything looks as needed to verify no sandboxes are overlooked for refreshes if needed.
3 votes -
Warn if source version is greater than the version of the target org.
Often, salesforce will deploy the latest API version to sandbox orgs before production orgs. Therefore it's easy to use API version 55 in your sandbox and then get a failure message when you try to deploy it to your production org which is at version 54. Unfortunately, you have to start to validate your deploy before you get this message. This could be a pre-deployment issue that you can notified right away.
1 vote -
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 -
Provide a better error when "invalid or null picklist values" is thrown.
"invalid or null picklist values" is thrown and i have too many picklists to figure out which one is the issue. Please provide speicific fields that are causing errors.
1 vote -
Show JIRA Title when selecting tickets to post to
As a release manager, when I go to select the JIRA tickets to associate to, I need to be able to see not just the ticket number, but also the Title to allow me to select the correct tickets without having to guess or consult another resource or use trial and error.
Currently there looks like this idea was implemented in Pipelines, but that interface is somewhat broken, and typing in the full number does not result in the ticket showing up, could use some love, but is the right idea for providing context.
1 vote -
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 -
API to export backup to S3 for data warehousing/datalake
A lot of time we would like to have data out of SF not just for backup purposes but for data analytical purposes as well. Ownbackup currently has this functionality via APIs.
https://documenter.getpostman.com/view/12146739/TzJuAxgY#0f1fc918-7616-4b58-8d52-0e8370f57d9b
https://ownbackup-kb.magentrixcloud.com/articles/knowledgebase/Using-the-OwnBackup-API-5-6-2020
If gearset has this, it would help us move to GS for all our SF problesms
2 votes -
Automatic Validation of Pull request for AWS code commit
Gearset does not support PR validation for AWS code commit. We are cloud-native and use AWS extensively, thus missing out on most important feature of gearset. If you can support it it will be amazing and lifesaver for us.
https://gearset.com/blog/set-up-automatic-validations-of-pull-requests/
3 votes -
Add or ignore parts of XML after the comparison to ignore other users changes
If there are multiple users making changing the metadata in Salesforce and when one has to deploy their changes, it is not possible to pick the changes that are specific to one person, For this we have to go to VS code and use git patch mode to add only the necessary changes for a specific user. If we have an option to edit the xml after the comparision and pick only necessary pieces and deploy it to next org will save time and also switching between multiple orgs. Currently the comparison editor is read only mode.
7 votes -
Archiving and restore process
Data archiving for storing records that can be easily accessed when marked as archived at an off-premise location. A backup and restore would be overkill when there is a need to store only partial records or a combination of fields from records in different objects. Restoring to a new object that does not interfere with existing objects would be ideal.
1 vote -
Ability to audit what users have done in Gearset
Hi, I suggest there should be a feature which monitors what the users within your orgs have done in Gearset. As we can currently are able to view both comparison and deployment history, however this does not give an audit trail of who has changed what and where.
For Example, the ability to review changes that a user has made to gearset comparison filters.5 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
- Don't see your idea?