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.
1314 results found
-
Allow searching for Org IDs in deployment history
Enable the search results in Deployment History to include Org Ids.
USE CASE: I want to see a history of all deployments into, or out of, a specific org, regardless of the usernames used to deploy.
BONUS POINTS: allow me to specify whether it's the ID of the target org or the source org when searching. ex -
targetorgid:00D1U000000sfXD
sourceorgid:00D1U000000sfXD1 vote -
enumerate unsupported metadata in Manage Custom Filters
In Manage Custom Filters dialog, Gearset should link to
a) https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_unsupported_types.htm
b) a Gearset list of Metadata API-supported but not yet GS-supported metadata typessaves devops person wondering why certain metadata can't be deployed
1 vote -
update the wording in the change notifications - objects created sounds like Salesforce objects, not individual items
We run change monitoring and were very surprised to have 218 Objects created in Production over the weekend when no one was working. It would be good to rename this to 'items' instead to make it more clear.
1 vote -
push new profile FLS entries into the profile file in alphabetical order
When picking up new FLS entries, by default these are added at the bottom of the list of FLS.
This causes issues when also having save jobs picking up changes, as this can result in duplicate FLS being added to a branch.
Please update code structuring, so new FLS is added in the correct place in the MD files.
1 vote -
Approval requests for CI deployments
It would be great if there is an automated approval process to deploy the code to higher environments. If there is a button "Submit for approval", and an email sent out to approver. that we can setup. once approved, a CI job need to run and deploy the changes to next environment.
1 vote -
Don't allow duplicate fields in comparison.
If I have a field with name example category. Somehow the same field has been added to the object xml file it needs to throw an error at the time of comparison.
1 vote -
Create a way to apply a regex to all currently selected metadata types when building a filter
The regex support you currently have doesn't really allow for complex (multi-match) regex matching, which is probably ok. (this would be something like grep -e 'this' -e 'that')
If I select, say 116 of the 124 metadata types identified, and then have to apply a regex pattern to each one, it gets pretty tedious. Click-paste-apply 116 times, and then 116 again for the other half of the complex match. I'd write a tool to automate configuring a filter in gearset. :)
If I "select all" then deselect the 8 types i don't want, and THEN apply a regex to all…
1 vote -
Allow filtering by Deployment Stage/Metadata Subset during comparison
This Gearset article describes some very logical phases for performing a large deployment:
https://docs.gearset.com/metadata-deployment-guides/splitting-a-complex-deployment-into-stagesIt would be nice if there were built-in comparisons to show each subset of metadata.
For example if you were on phase 1 of the deployment you could filter your comparison to just "Data Tier" and Gearset would pre-filter the relevant metadata.
1 vote -
Add functionality to select the changes in the component for the deployment.
I think it will be very helpful to have a possibility to deploy only some selected changes in the modified component.
1 vote -
Badge
To have he possibility to have badge that could be added to the readme of a git repo. Display in green if the test classes have been successful, red if error.
The same kind of badge could be used for deployment.1 vote -
When viewing comparisons, allow the "Export All..." to utilize existing filters
When viewing a comparison... I have various filters set to exclude certain differences like "Reports, "Permission Sets". It would be nice if you provided an option on the "Export All..." page to either export everything (disregard filters) like it does now, or to respect any filters that currently exist on the comparison so that I only see the values shown on the page based on my filters.
1 vote -
Retain Link to JIRA Tasks When Combining Deployments
Part of our release management policy is for all deployment to be associated with JIRA tasks. I noticed that when cloning individual deployment the association with JIRA tasks is retained. However, when combining multiple deployments, the relationship with JIRA is broken and as a result, we need to re-associate each JIRA task back to the combined deployment package.
1 vote -
Allow retrying failed validations and deployments
I'm often running into the situation where the validation failed either due to transient circumstances in the org, or due to the org settings being incorrectly configured. In this scenario, I would like to simply retry the validation using the same package, and I'd look for that option somewhere here:
https://app.gearset.com/deployments/validations
Running a new comparison (using the "clone package" option) is unnecessary, takes a lot of time. Also using the "view comparison" option is overkill. I would rather not go through those motions of recalling the comparison results from cache, going through the analysis once again, etc. Because I know…
1 vote -
provide creation of immutable deployment package
I would like a way for Gearset to create an immutable deployment package that can then be deployed to different orgs. This immutable package should contain a copy of the selected objects, list of unit tests to be executed and not allow variation in the deployment except selecting the target org. This would also save time by not requiring a new comparison to run for each target org.
1 vote -
Allow notification for long running jobs
Allow a for a notification to be sent when a Continuous Integration job runs longer than N minutes. Most of our jobs tend to complete in under one minute, so if a job runs longer than 30 minutes, being notified would be helpful.
1 vote -
Better handle Shares on Report and Dashboard Folders in pre-validation
during the pre-validation of a deployment, validate that the shares exist for report and dashboard folders. Currently if they do not exist in the target they fail during deployment. Only option today is to clean them up after error in source org and then redeploy. Instead, it would be useful if gearset removed them during the pre-validation.
1 vote -
Cruise control feed for Deployment Steps
We are planning to let our team notify and keep informed about the deployment steps status just that they can stay informed about it. These are non-Gearset users.
Can we have a monitoring feed for Deployment steps that take place from Compare and deploy Screen 1 which contains basic deployment details (Source and Target). So as an When we progress with the deployment steps, it will keep it updated. Similar what you have for Unit Test monitoring feed. (Test monitoring Cruise Control feed)
1 vote -
Suggest related metadata for selected types in filter
Gearset provides some very useful documentation on the importance of including groups of related metadata in a filter.
https://docs.gearset.com/metadata-deployment-guides/using-gearset-to-deploy-profiles
It would be very helpful if the Manage Filters dialog implemented these suggestions. For example, when a Profile is included in the filter, the user should be prompted to also select Profile Password Policy, Profile Session Setting, External Data Source, Apex pages, Layouts, and Custom Objects. Otherwise, the likelihood of Gearset assembling an accurate Profile without all of the related components will be slim.
Gearset obviously has deep knowledge of metadata semantics and dependencies. The Manage Filter page needs to reflect…
1 vote -
custom object translation of the Product2 object
The custom object translation of the Product2 object, specifically, is not behaving like the other custom object translations. So when I changed the label of this standard Object : Product2 (Set-up -> rename tabs and labels)
i can't find it in Gearset. I have to make this change manuelly.1 vote -
Clean up source/destination drop downs to be consistent across all UI elements.
The drop down lists for picking source/destination are different in the UI.
For example, in compare and deploy production salesforce connections are not in the list alphanumerically, they are appended to the bottom while in a clone deployment they are all listed alphanumerically.
Just being picky, but consistency one way or another would be great.
1 vote
- Don't see your idea?