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.
1148 results found
-
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 -
See Continuous Integration Deployments in the Deployment History tab
List deployments resulting from a CI job on the Deployment History tab along with manual deployments.
We currently deploy metadata using both manual and CI jobs and it would be convenient to see all deployments in the same list (for debugging, reporting, monitoring).
4 votes -
Allowing data deployments in CI jobs
Allowing data deployments in CI jobs. So that configurations in third party apps and B2B Commerce can be deployed as part of CI.
5 votes -
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 -
Delete records from the target org during a data deployment
Provide options to delete records from Target Org. This will help clean up of test data and reload from Source.
15 votes -
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 -
Queue Deployments
Current State:
A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org
1st Dev deploys work to .dev
2nd Dev deployment fails because org is locked
Idea:
A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org
1st Dev deploys work to .dev
2nd Dev deployment is queued up, 2nd Dev will be notified via email/browser when queued deployment has started
3 votes -
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 -
Add problem analyzers to the data deployment app
Much like the problem analyzers for metadata deployments in Gearset, it would be great if you could add a problem analysis feature for data deployments after having configured what you want to deploy.
Some scenarios will almost certainly cause the data deployment to either totally fail or only partially deploy some of the records and skip records it can't deploy. Providing automatic fixes (e.g. choosing not to include duplicates) would improve the number of deployments that work 100% of the time.
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 -
give the ability to ignore certain changes between Sandbox and Production enviornments
After deploying from a Sandbox to a Production environment, you will always see a 'change' for Custom Objects and Custom Fields because there is no Encryption Scheme (for example)
3 votes -
2 votes
-
Export snapshot of production org to git
I'd like to be able to export a snapshot of all the metadata from my production org (include all components) to my git repository by clicking a single button.
After every release, it's worth taking whole metadata export from the org to git for the next/on-going releases.
For now, we have to create a couple of metadata projects to export the metadata to git, which is a tedious job and takes a lot of time.
1 vote -
Filter on selected items
I want to quickly be able to identify components that have not been reviewed by only seeing unselected items in the "Changed items", "New items" and "Deleted items" top level filters.
seeing the ones I have already selected slows down productivity and I have to scroll through them. If I want to see them I can always look at the "All items" section. This information is also available in the difference type column.
6 votes -
add the ability to run static code analysis against an org or source control, simply click refresh button to re-run it and see results
This will give you a "run code analysis -> see results -> fix issues -> push to source control (or an org) -> repeat" workflow.
3 votes -
Possibility to deploy to another sandboxe when a ci job passed
When configuring a CI job, we need an option to set a deployment to another sandboxe when the deployment or test classes run successfully in the current CI Job.
Ex: when a push to a branch on VCS triggers a CI job to deploy to a sandboxe like QA (with test classes run), we also have the possibility to set an auto deployment to staging sanboxe when the the job on QA passed successfully.5 votes -
Show *all* matching items on All Items, even if they haven't been changed.
I couldn't find a field that I was looking for today, despite searching for it specifically, because it was hidden inside it's parent object. I understand that the reason for this was something to do with there being no difference on the field (and I appreciate that the reason is to avoid clogging up the screen!), but if you're searching for a specific field, I think it should really show up...
Took me bothering someone on live chat to figure out what was going on.
1 vote
- Don't see your idea?