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.
375 results found
-
Add a `Weekly` cadence to the test runner
I need to run my own tests (ie no namespace) daily as those should never fail and if they do I need to know
For namespace tests, I just need to run them weekly, primarily to reset the "invalid" flag on apex classes that can be tripped by trivial changes. I know some will fail as we have some huge apps installed and my understanding is that it's normal for dome of those managed tests to fail.
So I would only want to run them weekly to reduce the noise from the daily failure email. Just run those on Saturday.
11 votesYou can now schedule unit test jobs to run on specific days of the week, which means you can set up a weekly cadence setting the job to run on a single day.
-
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
-
Warn when deploying objects without profile settings
I build a VF page, test it, deploy it and discover much later that I forgot to add profiles other than system admin to the page. Users can't see the page and get a permissions denied error.
So, the suggestion is to have a an optional analyzers that warns when deploying a new VF page to a target org where the only permission is System Admin. While this could be legit in some use cases, in most use cases, this is a self-inflicted omission.
2 votes -
Filter comparions by date since x
The current functionality for filtering by date is welcomed, but I would like to suggest the ability to filter by date range.
Just some examples:
Date >= x
Date <= x
Date >= x and <= y2 votesGearset now has the ability for custom data ranges using a date picker, which should allow you to filter to all the examples that you’ve shown.
-
Specify friendly name before deployment
We would like to be able to specify the desired friendly name before a deployment completes, maybe above notes on the summary screen. The friendly name is copied from an existing draft, but when we clone from sandbox to sandbox and finally prod, there's no need to save a draft every time. Ideally, the friendly name would default to that of a cloned deployment as well.
4 votesThe ability to name the deployment from the pre-Deployment screen is now available, and will be used as the friendly name.
-
Allow me to exclude metadata.
I have certain metadata which is broken or dangerous to migrate from a dev org, I'd like to exclude it from this and subsequent releases. If I could 'right click' and ignore it that would be good.
20 votes -
Add context to the subject line for Gearset Deployment completed
The email to the submitter of a deployment has a subject line with no context. It reads: "Your deployment has finished"
Be great if it would say "Your deployment from <source name> to <target name> has finished". Especially helpful when user is manipulating many orgs and has to rapidly scan inbox.
2 votesWe’ve updated the emails to now include the orgs which were involved in the deployments.
-
Ability to select Field Sets as a separate item
It seems that Field Sets are deployed by deploying the object that they are related to.
This doesn't work well for me because I have admins changing objects in production, but I often need to deploy a Field Set to go with my code.
Currently, I'm jumping out of Gearset and deploying a Change Set with just the Field Sets, then coming back to Gearset to deploy my code.
It would be nice if I could select just the Field Sets and deploy them without changing anything else related to the object.
8 votesField sets are currently deployable as individual items assuming the object they belong to already exists in some form in the target. If the object the field sets belong to doesn’t exist in target yet, then it must first be partially created in the target for Gearset to be able to deploy individual sub components. Thanks for the suggestion!
-
Clone package dialog: run comparison button slow to respond and provides no feedback
When you click Run Comparison, there is no immediate positive feedback to the user that the button was clicked and Gearset is working. You don;t get any feedback until the screen is refreshed with the Comparison progress - and this can take 5+ seconds
0 votes -
Deploy detected changes to other orgs
Being able to detect and roll back changes to orgs through the change monitoring is cool, but what I'd really like is to deploy detected changes to other orgs.
For example, if we detect a new configuration change to Production, being able to clone that change back down into our Sandboxes directly from the monitoring snapshot would be a real time saver. Or if someone deleted something in Production, being able to make that destructive change down into the Sandbox.
It would help us remove the step of running the comparison and pushing the changes after seeing a monitoring job…
14 votesThis is now shipped and live in the app! We’ve written a small blog post that walks through the feature and the use case.
https://gearset.com/blog/migrating-quick-fixes-in-salesforce-to-source-control
-
"Run now" button for test automation
Adding the ability to kick off a test job on demand, rather than the daily or configurable frequency
9 votes -
Allow multi-selection of items with CTRL or SHIFT
It would be great to be able to select multiple items in a comparison using crtl or shift click, rather than checking the boxes one by one
8 votesReleased on 10th of Aug 2022
-
Org metadata snapshots
Allow a snapshot/backup of an org prior to running a deployment. Allow us to use this as a source of a new deployment if we want to revert any changes previously deployed, or at least download the package.
10 votesThis feature is now available. You can take snapshots of your metadata on-demand via the Change Monitoring feature and download the zip file created.
Use the local files option when configuring your comparison.
-
Ability to store elements selected during a Comparison for later use
Use case, before a deployment I determine which components I want to deploy, validate the deployment ... but then want to complete the actual deployment at a future date from within Gearset (i.e. once we get sign-off from the client).
Yes, I am aware you can download the validated package. I want to (ideally) complete the actual deployment in Gearset.
2 votesHi,
We’ve just released our ‘draft deployment’ feature in the app which will allow you to do just this.
Here’s how it works:
- Run a comparison as usual. From the comparison results, click Save draft deployment
- Your object selections and the comparison will be saved to your Draft Deployment history
- You can then return to continue building this deployment from your history at a later date
- If you’ve invited other users into your team, you can also edit and collaborate on their Drafts to build a deployment package togetherHope that helps,
Jason. -
CI deployment failure details in webhooks
Webhooks for CI deployment failures simply say "Deployment failed with (179/180 components deployed)" instead of describing the failure in more detail, including the Object and Error Message
6 votesDue to the potential number of items that could be listed we have restricted the number displayed to 12 since there could be hundreds, and provided a direct link to the errors page for convenience so it’s easy to view the full list of errors should there be more.
For the subset displayed, we’ve added:
- Item name
- Type
- Reason for error -
offer the capability to exclude items in a metadata filter using a regex pattern
If we can exclude certain things in the comparison filters, all other newly created things are automatically provided with the CI job that uses my comparison filters.
For example, at the moment in "custom filters", if I select the type "custom object" and disable "all elements", I can filter and choose which objects we want to compare.
-> We need the option to invert the filter. To be able to select the specific objects that do not want to compare and deploy (like "Not: regex: waste_ | QA_ | staging123_").
11 votes -
Be able to add the friendly name when adding a new org
Be able to add the friendly name when adding a new org as this saves going back to the list of orgs and adding then
1 voteOnce you’ve authorized the org, a friendly name field will then become available in the dialog to allow you to also specify its name.
-
provide a verification that a metadata filter is to be deleted.
It's far too easy to delete a custom metadata filter. When deleted, there is no way to retrieve it. Currently, I create backups of the filter by storing them with the same filter name and datetime. It's in case someone or even myself accidentally deletes the filter.
1 vote -
Ability to sort on the Change monitoring overview Page
From the Change monitoring overview page it would be helpful to sort by the various "Headings" currently they are not sortable at all.
1 vote -
Offer source branch update as option to trigger CI from custom Git (Gitlab in my case)
Please allow to select "when source branch updated" option in the CI jobs section when the source is a custom git repo
2 votes
- Don't see your idea?