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.
31 results found
-
Validation-only deployment for CI
Add the option to for CI to run validate-only deployments
2 votes -
Create the ability to migrate components to new source and target orgs after having in a Saved Drafts.
When saving components into drafts, when validated, we would like the ability to be able to migrate the same components into new source and target orgs.
8 votesHi,
You can now use the new clone feature for any saved draft deployments if you’re an enterprise tier user.
Regards,
Stephen
-
Be able to edit the CI sync frequency
When creating new CI job from one Salesforce org to another, there is no way to edit the frequency of synchronization. It would be useful to make a change so that integration is done less often than every 4 hours
9 votes -
Remind me what I just validated
I am working on 10 things at the same time like usual. I started a validation about an hour ago. I open the tab where the validation was occurring and it says it succeeded. Yippie! Problem is I don't remember what I was validating and nothing on the success screen tells me which system I was validating against. I want to be sure I am going to deploy the right thing to the right server at the right time.
Can you add the name of the destination system (at least) on the success screen so I can remember what I…
1 voteThis information is now displayed on successful validation.
-
Add column filtering with org type(s) in deployment history
Ability to filter on org and/or org type in deployment history so we can easily view which deployments were made to which orgs. For example, filter to only return deployments to production orgs.
2 votesWe’ve now added more advanced filtering to the deployment history page to enable multi-selection. You can find the filter menu via the dropdown next to the text search box.
-
Add button to go from validation package to comparison
Use-case is where we have validated a package, but not been able to deploy it before expiry. Eventually, we are able to deploy it...
At this point, I'd like to be able to go from my validation package in the history straight to a comparison with the same objects selected. Then, I'll be able to make sure everything still looks good and validate/deploy again.
1 vote -
Be able to create a CI Job with the option to validate only (and quick deploy later).
For the case where users have committed changes to a "master" branch, it would be useful to automatically run a full validation on the new commit in the Production environment. In that way, a deployment manager can review the changes and quickly deploy a validated package that has passed all tests in Production.
7 votesHi Nghi,
We’ve added the ability to review and deploy a validation CI job.
Catherine
-
Include/exclude individual metadata in templates by managed package
The Include Managed Packages option right now is a global one-- and, while nice, that doesn't cover situations where you want some metadata of a Managed Package (eg. a Profile permission) to be included, but not others.
Currently users have to laboriously deselect data related to Managed Package in certain areas (eg. Static Resources, Permission Sets, Custom Tabs) because it'll always fail to deploy.
The ability to include Managed Packages for some metadata, but not others, in templates would solve this issue.
9 votesWith Gearset’s named filters, you can now configure exactly which metadata components are going to be included in a comparison.
For the advanced use cases, you can also use regular expressions to define rules that, for example, include all managed components that match a certain naming convention.
You can find the docs on our site https://docs.gearset.com/feature-guides/comparisons-and-deployments/custom-metadata-filters
-
Add a Save As to Save Draft Deployment
Add a Save As or an alternative way to create multiple packages from the same comparison. I have an existing comparison run and I want to stage the deployments, deploying some today and the rest next week. It would be more efficient to save both packages now as I am going through them, saving one for example as Dep120916.1 with half of my selected object and another one called Dep120916.2 with the remaining objects to be deployed later.
13 votesFrom the results page, you can now select the Save as option from the button toggle menu.
-
Rollback deployments made by CI jobs
Manual deployments and change monitoring jobs can be rolled back. Add the same function to CI jobs in case it accidentally deploys something unwanted
27 votesWork completed on December 22nd, 2021
-
Combine multiple deploy packages into one
It would be nice to have the ability to select multiple packages in the deployment history, and clone all of them into one comprehensive deployment. This would help when there are multiple features moved at different times to a QA environment, but would like to move them all at once to Production.
28 votes
- Don't see your idea?