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
-
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.
6 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 -
Jira comment only for production releases
We would like to have the option to choose which deployments create Jira comments. As business users often watch our Jira tickets, we would prefer only posting comments when we actually "release" (deploy to our production org) and skip comments for releases on sandbox environments.
13 votes -
whenDeploying metadata and linking it JIRA Issue it will be good idea to have more Jira Issue fields visible not just Jira Issue key(id).l
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 -
When creating a Pull Request from Gearset have the option to default to another branche
After you did a deployment from a sandbox to GIT (Github in my case) you have the option to create a Pull Request right from that screen. The default target branche is "main" even though my default branche in Github is set to develop.
It would be great if Gearset follows that default branche that is set in Git OR has a way of defining default target branche in Gearset.
The risk now is that someone might overlook this, make a pull request against main, someone else also overlooks this and merges it into main. With CI jobs on main…1 vote -
Provide help link/button on each analyzer problem pane with specifiec discussion
Suggestion
In "Problem Analysis" page, the problems indicated and solutions are not necessarily obvious and understandable.The suggestion to read more about the analysers in the user guide is in the case I'm facing an enormous challenge.
Copy and paste the problem into your search mechanism brings back endless answers - not one used the wording in the problem statement!.
Here's an idea, have a button/link with each problem that take one to the user guide section (or other documentation) exploring the problem.
No hunting for answers as the 1st choice to figure out what your product is saying. It's…
1 vote -
Additional feature - GITHUB Pull Request validation in CI Job
Checkbox - Pull requests: Validate pull requests targeting the source branch is only visible when Run Job is set to --> Run tests based on Apex changes in the package
Request you to enable option even when this is set to Run Job: 1 / 2 /4 / 24 Hours
1 vote -
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 -
Add csv file results as attach
attach a file to Teams after code analitics with incoming Webhook
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 -
Add Comparison Column for "Environment"
Add a column for "Environment" which signifies which environment the change took place. For instance, this would tell you whether the changes took place in Production Only, Sandbox Only, or both.
Then, I could filter by Sandbox Only and both to see only the changes I made recently in the sandbox that I need to push to Production. Right now, I have to sift through the many little changes to items that occurred in Production.
1 vote -
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."
1 vote -
Approval process for metadata deployment
It would be great to have a approval process for the deployment.
For example, once we have completed the comparison and validation, we can click a button "e.g.: Submit for Approval" and an email will be sent to a list of email.
In the email, receiver can review the summary of the deployment (e.g.: source org, target org, number of changed/new/deleted components, ...) and click on a link to approve or reject the deployment.
We can deploy only when the job is approved.4 votes -
Add a 'flag' to ignore XML 'utf' versus 'UTF' in XML header.
I believe there exists a mismatch with the XML header reference to UTF in the Gearset library to what is used in SFDX.
6 votes -
Ability to accept/disregard repo cleaner changes
I would like the repo cleaner to work more like the problem analyser, offering a chance to accept or disregard the suggestions before executing it.
Currently Repo Cleaner can only be enabled/disabled only at team level settings, thereby forcing the setting team-wide, which effectively rolls onto all the projects/repos using Gearset for deployments.
I have come across a situation where I would not like to alter the repo with changes any more than what I have actually changed, but since its a team-wide setting the repo cleaner was getting triggered in and bringing in more changes to my repo than…
6 votes -
Compare Active Version of flows not the newest Flow
When comparing flows please compare the active version of flows, not the newest version. This would align with how change sets handle flow.
Example:
Version 2 and 3 exist in source. Version 2 is active and version 3 is draft. I want to deploy Version 2 that is active not the inactive flow.10 votes
- Don't see your idea?