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.
270 results found
-
Meta Data Searches
Ability to do a meta data search like you can in eclipse or visual studio in gearset.
For example search a custom field and where it is used within your org.
1 vote -
How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?
How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?
2 votes -
Create an rss or atom feed as you add new features
When working inside of Gearset, it often alerts you to changes that have been recently made. It would be nice to have these as a separate, consumable, feed. We have a slack channel that we would like to pipe those changes to, for instance.
2 votes -
Allow save into a draft deployment after Refresh Comparison
Use case:
Source is master, target is org
Create draft deployment between master and org; Save
...time passes, new items are added to master
Open draft deployment
Refresh Comparison to see new items in master
Select new items
Click Save Draft Deployment --you have to create a new version (and no obvious way to even see the current draft's name without opening a new tab)Seems like you should be able to save back into the same draft after refresh comparison (or at least have option to do so).
When you create a new version of the draft; you have…
18 votes -
Ability to chose multiple targets for a deployment
It would be nice to be able to deploy to multiple environments all at once from one source.
35 votesWe're currently reviewing how we can facilitate deployments to multiple Salesforce instances simultaneously. Please let us know how you manage this currently, or how you would like to manage it - thanks!
-
Provide an option to run Aura and/or LWC testing before deployment
I don't think that very many people are actually creating Aura/LWC tests yet, but they really should be.
Since SF doesn't require them like it does for Apex, if we decide that those tests ought to be run before deployment, it would be great to have Gearset run them. This will help us to make sure they are run before every deployment instead of relying on developers remembering to do it manually.
5 votes -
Combine multiple daily monitoring results into a single deployment
If you want to deploy the differences of an org on a weekly basis, it would be a great option to take the monitoring results of the last 7 days into a single deployment.
Especially in huge orgs, where comparism takes 30 minutes time to show up, this would ease deployment pretty much.2 votes -
Provide the ability to run static code analysis on all commits to the repo
We'd like the ability to run static code analysis on all commits to a repo, regardless of the branch name. This would allow us to catch code quality issues early and up front, regardless of the branching model we use.
Example: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow (development is done in feature-* branches, so there's no one branch we can configure a CI job on)
1 vote -
Gearset to do Sanbox Refresh by copying metadata and data from production
Quite often an Environment needs to be refreshed, but every time it happens all the integration breaks as OrgId changes. Gearset can move metadata and data, which when made together can be a solution for sandbox refresh. Full copy sandbox sometimes takes days, GS will be able to it quite quickly.
1 vote -
Adding Custom destructive
ANT is unable to change the type on an EmailTemplate from HTML to CUSTOM. To solve that we need to add the EmailTemplate first to the destructive package to have it removed and then add it again with the package.xml
Since this file is not deleted but just changed. It doesn't show up in the deleted items tab.We should add an option to the "Selected Items"/"Changed Items" list to opt-in for adding that to the destructive.
12 votes -
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 -
Use the information in a JIRA ticket to select the components to deploy
Instead of manually selecting components to deploy. If we have an integration with JIRA and the components are listed on the JIRA ticket. Would it be possible to then specify JIRA tickets to deploy and have Gearset automatically build the deployment package?
2 votes -
Enhance the deployment history search functionality
When trying to gather packages together to combine them for a release, currently it is not possible to first limit by a text search then expand the date range (search hangs due to number of retrievals)
Could there be a way to enhance the history search to enable easier searching?
2 votes -
Give users the ability to update field/object permissions for specific profiles only
The issue is, when promoting from one org to another and changing either Custom Object Permissions or Custom Field Permissions and if more than the profile you want has been changed, the extra profile changes get promoted anyway. So we need a way to control which profiles get applied when promoting field and object level security.
3 votes -
Show Created By and Created Date when doing comparisons
When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well
6 votes -
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 -
Need to move Help Menu between orgs
I recently had to move custom Help Menu items between orgs. Since Gearset didn't support it, I was reduced to manually entering the data in each org since they weren't connected in Change Set paths. I believe the metadata is CustomHelpMenuSectio
2 votes -
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 -
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 -
Problem analysers - to ignore the user config element
On metadata deployments, I frequently struggle with Report Folders, Workflow Updates, and other configuration elements that have individual users assigned to them. The struggle is that individual users assigned to these config elements often do not exist in the target org. This results in the entire deployment failing, and many times, manually configuring the report, report folder, etc.
A nice solution to this would be a new section on the Problem analysis screen that allows me to exclude the users from the config element that is being deployed.
It is useful to call these scenarios out, because I need to…
1 vote
- Don't see your idea?