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

360 results found

  1. 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 →
  2. 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

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

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

  5. 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 →
  6. 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 →
  7. 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

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

  9. 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 →
  10. 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 →
  11. 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.

  12. 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 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  ·  Testing  ·  Admin →
  13. Ability to compare and migrate object data between Salesforce orgs

    The metadata compare and deploy is outstanding and works well. What would save configuration and release engineers even more time would be an object data compare / sync. Sometimes, salesforce releases may only require a data migration. Hopefully, this feature will get a few upvotes from the community as well.

    14 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. Filter on Columns in comparison screen

    On comparison screen, would be nice if we can filter on each column on top of standard string filter

    Example use case: Show me Custom object with last modified by me with modified date within this week.

    Can be achieved if we can filter on "metadata type", "Changed on", "Changed by" Columns

    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

    We’re closing this feature request as the main bulk of functionality (more advanced filtering on a per column basis) was implemented at the end of 2016.

    If you have a specific interest in 1st class filtering specifically by date, could you open a new feature request for that?

    Thanks,
    Gearset team

  15. Add a 'Share Organization' shortcut under 'Actions' in Manage Organizations

    For team members without access to a saved organization, the hover tip on the inactive 'Open Draft' button in Draft Deployments reads "You don't currently have permission to edit this draft. Request access from the owner of the source and target credentials".

    If the org owner looks under 'Manage Organizations' to remedy this, there's no information on this page indicating how to grant access . Most users on our team are Account Members (not Account Owners), and not familiar with navigating the 'Account' menu options.

    Would suggest a 'Share' shortcut under Actions in 'Manage Organizations' to take the org owner…

    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

  16. Exporting Scheduled Test Results to File

    We would like to see the ability to export the scheduled test results to PDF or Spreadsheet. This will allow us to associate test results with our internal work items and allow visibility into the test results. I understand that users can view the test results with no license. However, i see value in having the export available; similar to the export of the deployment report.

    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

    1 comment  ·  New feature  ·  Admin →
  17. Have CI jobs work using BitBucket webhooks

    Just like it is already with GitHub.

    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

    1 comment  ·  New feature  ·  Admin →
  18. 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

    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

  19. Text results on Monitoring to multiple phone numbers

    Allow text message notifications to multiple phone numbers

    3 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

    0 comments  ·  New feature  ·  Admin →
  20. CI Jobs - Partial Deployments

    Allow partial deployments when changes are committed into a branch, so instead of trying to re-deploy the full repo, we should have an option to allow deployment for only the changed items.

    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

    1 comment  ·  New feature  ·  Admin →

    CI jobs can now be set to deploy only certain types of metadata change: new, changed, deleted. If only “changed” is selected, no new metadata or deletions will be pushed by the job, only modifications to metadata that exists in both source and target. This selection is found in the job creation/edit screen. You can also specify whether you want the CI job to respect a package.xml file when deploying from a repository for even finer control over what metadata it deploys.

  • Don't see your idea?

Feedback and Knowledge Base