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.
81 results found
-
Ability to deploy remaining Omni-Channel Components
For Omni-Channel deployments, QueueRoutingConfig metadata type is now supported by Gearset. However, corresponding PresenceUserConfigUser and UserServicePresence metadata types are not yet available. This means a secondary Metadata API tool (e.g. ANT, Workbench) or other manual steps are needed to complete an Omni-Channel deployment.
Hoping all supported components for API deployment can be included in diffs for releasing all via Gearset.
5 votes -
Keep the Deployment Friendly Name / Notes when you refresh a comparison
Keep the Deployment Friendly Name / Notes when you refresh a comparison
5 votes -
Output information after CI Job regarding problem analyzer skipping some component deployment
I would like to get some information from the problem analyzer after a CI Job completes as it seems like if it detects a problem during the job it skips deploying some of the components, like user permissions.
5 votesYou can now see this under [View problem analysis fixes] for each CI job run.
-
Add a "Clone package" button to the Deployment Results page
My workflow is currently to deploy a change, browse to the deployment history to find my deployment, and immediately clone the deployment for another environment. It would be really nice if the clone button were available upon a successful deployment.
5 votes -
Ability to pause CI jobs
Ability to pause a CI job. This would allow the CI system to keep our sub environments (stage, dev, beta) updated all the time, but when we want to develop on one of them we could then pause the CI job so our changes don't get deleted. Then once we have deployed the changes to prod we can reactivate the CI job to keep things in sync.
5 votes -
Allow GitHub to be a Target, not just a Source!
Let us move changes to GitHub!
5 votesWe’ve now shipped the ability to choose GitHub, Bitbucket and GitLab as the target for deployment.
Simply pick the Source Control option on the target when configuring the comparison.
-
I would like the option to view the delta CI only changes within the comparison, like the agents who are helping me untangle issues
I would like the option to view the delta CI only changes within the comparison, like the agents who are helping me untangle issues. ask kevin slattery to show you.
3 votes -
Show deployment friendly name on Deployment successful page
On the "Deployment successful" page, I'd like to see the Deployment friendly name displayed. This would be much more useful than the Salesforce Id that is currently displayed.
3 votesReleased this week
-
GitHub Pull request
All user to submit pull request from within Gearset instead of having to jump out to GitHub.
3 votesWe’ve now added the ability to create a pull request for GitHub when the deployment has succeeded within Gearset.
You can read more about it from our blog post: https://gearset.com/blog/create-pull-request-in-gearset
-
Add a "Clone Package" to the Validate packages tab
Allow users to clone a validated package just like that can clone a deployed package.
3 votesWe’ve now added a dedicated Clone Package action to the validated packages table for Enterprise users.
-
Run Tests During CI Jobs
There are some similar but not exact posts below so I'm writing about a new one. We would like to be able to specify an option to run tests when deploying via a CI job from git (Bitbucket) in our release sandbox. If any of the specified tests fail, the CI job would fail and the deployment rolled back. It would be great is we could specify whether to roll it back or not when configuring the job but if that is too much too bite off, just failing the job would be helpful. Thanks!
3 votesIf you edit your CI job then you’ll have four options:
1. Default test behaviour
2. Don’t run any tests
3. Run only your tests
4. Run specific testsYou can select the test level that you’d like for your CI job and it will be respected and pass/fail your CI job accordingly.
Thanks for reporting and I hope this helps!
Kevin
-
Add Lead conversion support
Please add support for the LeadConvertSettings metadata.
See https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_leadconvertsettings.htm for details3 votes -
A way to view failed deployments from Gearset
Right now if a deployment fails in Gearset, it doesn't show up anywhere within Gearset; it just sends you an email. It would be nice to have a place to view failed deployments and retry them (maybe it only failed because the environment was locked), just like you can with successful deployments in Deployment History.
3 votesGearset now shows failed deployments on the deployment history page: https://app.gearset.com/deployments/deployed
-
Text results on Monitoring to multiple phone numbers
Allow text message notifications to multiple phone numbers
3 votesYou can now add multiple phone numbers to receive text notifications for Monitoring and CI jobs.
-
Desktop notification when deployment is complete
When you launch a deployment to a target org the browser tab (which will be one of many in your browser) shows Depl...
Since the user is multi-tasking, it would be helpful to add a desktop notification and change the browser tab to alert user when deployment is done (like what Gearset does when a comparison is completed)
This could be a D ✅ or D ❌ depending on whether deploy succeeded or failed
2 votesThis has now been released, with notifications for both failed and successful deployments.
Thanks for the suggestion! -
Support flow deletion at V44+
if the target flow is deactivated; and all prior versions are deleted, you can't delete the last remaining flow version in the target org. The error you get is "Insufficient access rights on cross-reference id".
Copado provides a solution (https://docs.copado.com/article/8l069zes9f-destructive-changes-in-copado-doesn-t-support-flow-and-process-builder) wherein the user can specify the contents of the destructive-changes.xml file (enumerating the versions to delete) but Gearset has no way to inject such a file into a compare/deploy (esp a CI deploy)
with SFDC pushing more and more dev into Lightning Flow, deletions are inevitable in many orgs as things get refactored/renamed
2 votesWe have added a problem analyzer that will detect when you are deleting a flow, and update the destructive changes xml to include all the versions automatically.
Thanks for the suggestion!
-
Add support for CMS Connect Sources
Please add support for CMS Connect Sources in the comparison filters as well as the deployments and CI jobs.
We're working with CMS Connect in our current developments of a customer community and we'd like to deploy this metadata as well.
See the metadata api documentation: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_cmsconnectsource.htm2 votesWe have now added support for the CMS Connect Source metadata type.
-
Select more than one item at the same time
On "Items to include/exclude for Custom application" view, it would be really nice if we could select more than one item at the same time, using SHIFT shortcut.
When clicking on "Named Item", and if you want to select from the 49th line to 63th line for example, and to avoid to select manually 15 lines with 15 clicks.
We could just select the 49th line, and with SHIFT, click on the 63th line to select them.
Thx2 votesReleased on 10th of Aug 2022
-
There should be an option to schedule unit test jobs weekly in Gearset
Hi Gearset,
I would suggest you to provide an extra option where we can select weekly ,daily or monthly schedule jobs in Unit Testing Jobs.Thank you,
2 votesYou can now choose which days of the week a unit test job should run, allowing you to schedule the job to run weekly.
-
Update the CI Jobs Page so you can organize, similar to Deployments History page.
We have a bunch of CI Jobs, and it gets a bit difficult to identify whose job is owned by who just by looking at it.
Maybe make it similar to the Deployment History tab where I can sort out things by clicking the options above like "Owner" or "Name" and it'll organize it the way the Deployment History tab you guys have in place.
2 votes
- Don't see your idea?