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.
1235 results found
-
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 -
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 -
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 -
Delta only validation CI jobs
Idea is to have the Delta CI for Validation only Job, so the as well, so the validation process will become faster .
The option of validating a PR in the deployment job does the same task, but is comparing too many items of metadata and it is taking too long.
14 votes -
Delegate Access by Comparison
Provide an additional delegate access option: be able to grant this at a comparison level to a user vs at the org level (situation is predominately experienced for Production comparisons/deployments). Granting access at an org level gives too much access (CI jobs, etc) for some users so it would be ideal to have a narrower scope.
1 vote -
See when a commit validation was deployed or not (For CI validation Jobs)
When you go to the validation only CI jobs section within the Continues Integration part we usually have a CI job targeting a prod environment, you can see all validations succeeded and the commit attached to such validation, each CI job run contains 3 options:
View comparison
View Summary
DeployThen if the validation passed and the code indeed was merged from the feature branch to the master branch (Which would have triggered the actual CI job run), how would you be able to identify wether a merged pull request was deployed or not within gearset?
For me it's very…
1 vote -
Expose Salesforce Validation Errors within Github PR
Currently when a PR Validation fails (Deploy CI Job with Validate Target setting turned on), the user can click the Gearset "Details" link to go into Gearset to see the exact error.
Many of our devs use VS Code and Github for their daily work and only rely on Gearset for the CI job. Having them jump into Gearset just to see the error is time consuming and not very intuitive for them. Sure we can find the same errors within the target org of the CI, but at that point the list of validations is large and it's hard…
8 votes -
Allow the creation of CI Jobs against Salesforce orgs that we are delegated to, instead of needing to be owner.
We have 2 admins that we want to be able to create all of the CI and Pipeline Jobs, even if they don't have their own credentials in a particular Salesforce org. They have Deployment delegation, and can run compare and deploys, but not set up integration jobs.
This is then requiring us to either, provision extra licenses in each sandbox for our DevOps administrator, or have the developers create the CI jobs, which they are not comfortable with.
And, as we start the Pipeline Pilot, we would like to leverage all of the existing CI jobs, but, that is…5 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 -
Create GitHub App as alternative to GitHub OAuth
Gearset currently uses OAuth to connect to GitHub, and the way that works is that the OAuth connections have permissions to all repositories that my user has access to, which from a security perspective is a problem, because if the github key were ever compromised, it would provide very broad access to customers GitHub organizations.
Security teams would feel much better with the ability to limit the scope of access to just one repo instead of all the repos that my GitHub user has access to, which can be accomplished by creating a Github App which can be installed for…
10 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 -
New Feature: Filter Custom Fields (and other sub-components) in Comparison Filters
I'd like to be able to exclude certain custom fields from my comparison.
For example we have fields that have environmental differences between orgs that we don't want to deploy. There are also random fields on standard objects that show up as "different" even though they aren't and it would be nice to filter them out.
4 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 -
Create JIRA ticket when CI Job runs sucessfully
I undrestand that gearset can update status, comment and attach report to an existing JIRA ticket once a deployment is successful, but it would be nice to have a feature that would automatically create a JIRA ticket once the CI Job runs, and deployment is successful, for reporting and internal auditing
1 vote
- Don't see your idea?