Help us improve Gearset

Welcome to the Gearset feedback forum. We love getting feedback from our users on how we can make Gearset even better.

Post your ideas and vote for others – let us know what’s important to you. We’re keen to hear about product improvements, new features, and bug fixes alike. We check this forum regularly and will keep ideas updated with their current status. If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Adjust dependancy on managed package versions for Apex[Class|Page]

    We've found when developing classes against managed packages the class ...meta.xml includes the package version numbers. Problem is these are fixed to the exact version installed (e.g. 9.4, 9.3 etc. example below)

    But then if the managed package is upgraded Salesforce, in its infinite wisdom, doesn't update these so when you come to deploy next time you have to go and manually update all the version numbers - or if you have a different version in another sandbox (to test the newer one) same thing.

    Seems like something a cool deployment tool could handle and offer to fix up on…

    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

  2. integrate with Atlassian Stride for notifications

    Gearset's ability to send notifications to Slack is great. I'd like a similar ability to send notifications to Atlassian's Slack alternative - Stride.

    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

  3. Add deployment support for Macros

    Macros deserve to be added to source control yet there is no way to do this with Gearset:

    1) Data feature (paid add-on) doesn't deploy to/from source
    2) PRO/Enterprise can't source/target deploy Macros because it is not available with the Metadata API.

    Since macros represent some debugged logic, managing in source control makes sense. Curiously, SFDC has chosen to make Documents available via Metadata API but not Macros

    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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Trust Site

    Right now, Gearset is down and we cannot use it. It would be good to have a trust.gearset.com site that shows what is going on and what the team does to fix the issue...

    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

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  5. Avoid spurious Analyzer message when deploying external objects (e.g. Foo__x)

    If you create a new org, add an External Data Source, add External Objects, and deploy to a target (source control), you will get this spurious analyzer message:

    "Some standard object fields which don't exist in the target organization are being deployed, which indicates they might use features not enabled in the target. You need to remove these from the deployment, otherwise it's likely to fail."

    and all your external objects are enumerated, e.g.

    Ordersx
    Customers
    x
    ...

    These are not standard objects, and, as they are new, would of course not be in the target. Analyzer is being…

    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

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  6. When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist

    When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.

    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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow for custom metadata permissions to be included with a single click when custom fields are being deployed

    For example; when adding new custom fields, you generally have to add the permissions as an additional line item to the deployment. Having a checkbox or something that will have gearset automatically add the permissions associated with the metadata currently in the deployment list would speed up the process. Users should also be allowed to deselect lines that were automatically added.

    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

    3 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  8. Build Comparison Manifest from pull request

    It would be cool if the custom deployment configuration could be driven from a Pull Request . For example, in GitHub, the Pull Request knows which files were changed and approved. Why not use that list to instantly populate a comparison to create a deployable manifest to go from source control to org?

    15 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  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add Run all tests except .... configuration in CI job

    Our CI jobs take way too long (1000+ tests) despite heroic efforts to use ApexMocks. As our org contains a bunch of unmanaged packages with known class name prefixes, and these constitute at least 10% of the total tests; we could get back 10% of our life if we could exclude these from the "run only your tests"

    For example, we would want to exclude running any tests in classes that start with "fflib" and "sfab"

    A variation of this would be to run a specific testSuite and it would be our responsibility to keep the testsuite up to date

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  10. Ability to have automated process to maintain field list in Production environment

    With GDPR, companies are required to provide justifications for all data that they collect. In Salesforce this means being able to identify why all fields in the system exists, categorize fields as PI, and provide business justifications. The ability to keep a list of current fields in a production instance of Salesforce that includes alerts when new items are added, or ability to sync that list out to another tool like Smartsheet, where other business users like a legal team would have visibility, would be incredibly useful.

    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

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  11. Restrict source orgs

    For example, deployments to a production environment should only come from the master branch of our git repository

    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

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

  13. Allow (restricted) editing of source XML to add deployable properties that can't be fetched via Metadata API

    related to: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/14808303-allow-source-metadata-to-be-customised-prior-to-de

    Example:
    It is impossible with OOTB Gearset to deploy an autonumber field with a starting number and optional populate existing rows. Why? Because the SFDC Metadata API as of V42 doesn't allow fetching of these two properties of the CustomField object:

    <populateExistingRows>true</populateExistingRows>
    <startingNumber>1</startingNumber>

    Once in source, they'll deploy just fine to the target org. Note that changesets support this feature.

    The workaround, which is to deploy to target branch and then edit target branch is sort-of-OK but it would be nice to modify this in the source. Of course, if you Refreshed Comparison, your edits would be…

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to add custom trigger points to trigger CI from source control

    At the moment the tool allows you to only kick off CI jobs when a branch is updated.
    This is actually limiting the capability of the tool in itself,
    because services like Bitbucket allows you customize trigger points, as to when they should ping the webhook;
    such as the creation of pull request, merging a pull request.

    The two trigger points mentioned above are specifically very important because you would want to run validation CI jobs on the creation of pull request or when the merge completes so that you can actually ascertain if your branch compiles.

    Based on an…

    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

    5 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allows admins to limit the available branches of a repository

    When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.

    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

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow repeat/redo deployment from Deployment History

    Use case:

    1. Deploy from source to target
    2. Some testing (or possibly PR review) in target requires fixes to be redeployed from source to target

    Currently, you either do a new Comparison or clone the Deployment and re-enter the source and target. In either situation this is tedious.

    Why not add a "Redo" button on the Deployment History that uses the same source/target? Place it next to the Clone button?

    Or, in the Clone button, default the source and target to the same as the selected Deployment? (which would also be useful)

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  17. When source is local files, Refresh Comparison button should be smarter

    If your source is Local files, and you do a Compare to some target, and then realize the source needs to be amended before re-comparing, your "training" is to clock "Refresh Comparison" button.

    This executes but does not ask you to upload new source files so essentially nothing happens.

    User should be given option to upload new folder/zip.

    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

  18. Add an option to use a custom "Gearset format" for the source control output

    The XML that comes from Salesforce is weirdly bundled together. When changes are made it's really hard to reconcile two branches in source control when merging.

    When comparing, Gearset nicely decomposes changes into smaller chunks. So instead of putting that back into the usual XML, an option to store that "internal format" and even just stick it as JSON or similar.

    After all - it'll be Gearset reading it back in to compare to an org next time, and smaller changes will be easier to merge as they won't conflict inside horrendously large XML files

    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

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  19. Deploy parts of Settings

    It would be nice if you broke up the settings into smaller subcomponents. For example the Security settings would be more useful if you extract out the password policy changes so we can pick and choose what Security settings we need. I thought of this concept similar to how you break up profiles into sub component. This could get noisey in the list of changes so an alternative to that could be to bundle it under components like how CustomObjects work.

    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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  20. Indicate whether a Validated Package is enabled for Quick Deploy

    T0 - You Validate a package to PROD (run all tests)

    T1 - You or someone else does a deployment of something else, no matter how minor, to PROD.

    T2 - You click Deploy of the Validated Package from T0, all the apex tests are rerun. This is by design per SFDC yet Gearset doesn't tell you in advance that Quick Deploy is not available. Something you think will take a couple of minutes now takes 30 minutes or more. You think you screwed up or Gearset is broken

    Suggestion: On Validated Packages page and on the page of a…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base