Skip to content

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.

If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

369 results found

  1. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. Be able to require a commit message for deployments

    Sometimes a user may forget to add in a commit message before deploying, so the history in our source control is "no commit message" which is not editable. Can we add a feature to be able to turn on marking commit messages as a requirement for deploy?

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  New feature  ·  Admin →
  3. Allow scheduled jobs to be assigned a different authentication user

    We would like the ability to change over scheduled monitoring/testing jobs to a different authentication user. Currently if we need to switch an authentication we lose the history.

    Consider:
    I leave my employer and I need to switch the monitoring over to another developer or admin. I have to delete all the current scheduled jobs and re-create them using the other users authorization. Which causes the history to be lost.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. Add org name column to deployment history

    We currently have to prefix the deployment friendly name in deployment history with our sandbox/org name to be able to sort by target. It is not easily filtered either as the name column includes both source and target. We would like to have the target org as its own column in deployment history, and have it use the org friendly name as the value if one has been set.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Completed  ·  10 comments  ·  Admin →
  5. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. GitLab for destination of comparaison

    I can't compare my sandbox org as source against my git repo as destination of compare.
    I can see : gitHub, bitBucket as destination but no Gitlab.
    It would be nice I if I could choose Gitlab as well and update my repo from changes in my org.

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  7. View deployed components from a CI Job

    Display components deployed via a CI Job. In my case, there are a greater number of total objects deployed than I would have expected; but, I have no way of viewing the comparison for what is automatically being deployed.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  8. Add support for Visual Studio Team Services git repositories (Hosted TFS Git)

    We use VTFS for version control hosted or OnPrem SVN for version control. Our enterprise architecture team has determine those are our 2 options for source control and Gearset doesn't support those options.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Completed  ·  6 comments  ·  New feature  ·  Admin →
  10. Add the ability to define which Apex Test's are run during the validation phase of a deployment

    I would like to suggest a new feature request. We have a great need to define which apex tests are run against the Target ORG due to special configurations. We have apex classes / test classes that are created in Target ORG's that are client specific. For example, if we go to deploy our managed package from Sandbox A -> Sandbox B, the tests may fail since the content in Sandbox A needs to get to Sandbox B before the client specific changes can be updated / tested. There are multiple parts to our product and adding in the ability…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Completed  ·  1 comment  ·  New feature  ·  Admin →
  11. Allow search-based excluding of metadata for templates

    Sometimes we have individual metadata that must be excluded-- every time-- from releases, without excluding the entire metadata category.

    For our organizatin, for example, we want to exclude "Search" every time due to an error-- but we don't want to exclude the "Settings" metadata item.

    It would be great if we could add specific exclusions to the template so that a specific metadata item would not even pop under the Compare screen. Doesn't really matter how it's done (fuzzy searching or specifically excluding standard items) to me.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    With 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

  13. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. Be able to create a CI Job to auto-commit (changes between two orgs) to source control

    We have both admins and developers working within our SFDC environments.

    Admins typically deploy across environments, so being able to create a CI job to keep the repo updated with these org-to-org changes would be ideal.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Admin →
  15. Create CI deployments which only run on demand

    Have jobs that run only manually, rather than on time or commit basis.
    Specify the source and target and the metadata filter, and save as a preset job. The job can then be triggered to run on demand with a "Run now" button. This means we can safely update our branch until ready to deploy, then don't have to manually compare orgs to push the changes out

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  16. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  17. Under deployments in the validated tab there is no column for the name of the deployment. Please carry over the friendly name.

    When a draft is validate, as the gatekeeper for production I cannot see what a coworkers validated deployment is about. It seems like the friendly name should carry over as a column to display on the validated tab, also into the deployment history.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    This is now implemented and released. As on the deployment history page, you can now name your validated packages.

    This name will follow over from a draft deployment and to the deployment history.

    Thanks for the feature suggestion!

    Oli

  18. Remember a default Github repo

    I have access to a huge number of Github repos but use only one for gearset deployments. It would be nice if that repo were automatically selected.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Completed  ·  3 comments  ·  Admin →
  19. Disable scheduled tests (temporary)

    We're currently using this tool primarily for nightly unit test monitoring. However, some nights we don't want the tests to run because we'll be doing after-hours upgrades and other maintenance.

    As far as we know, currently the only way to 'disable' the automatic test run is to delete/disconnect the app entirely. However this is not ideal, as we have to re-add/re-auth to turn it back on.

    If Gearset had a checkbox next to each org/environment that we could enable/disable the job at will, that would be ideal.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Testing  ·  Admin →
  20. add linked services to "Reuse deployment package"

    When cloning a package that was originally deployed to a github repo, the dialog for "Reuse deployment package" only has source/destination Salesforce organizations and not linked services like github.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks for the feedback, this was a great suggestion. We released this feature last night – if you clone a package you should now have the option to choose from Salesforce orgs or linked services such as GitHub.

  • Don't see your idea?

Feedback and Knowledge Base