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. have functionality to show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB

    I suggest you have functionality to show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB

    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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow Package Cloning between Saved Comparison Pairs

    Please allow us to select a comparison pair as the source/destination when cloning a package. This will make it much easier to select the source and destination when cloning a package, and reduce the risks associated with accidentally selecting the wrong repo or branch or sandbox.

    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. To add capability to mark (to ignore) not selected items to be able to remember that the particular item is not required to be deployed

    When compare source and target, sometimes u do an educated decision to NOT select something, and then selecting the rest of the items. Then if the compare results saved as a Draft Deployment, u may return back to it, and do a refresh for the comparison. In this case Gearset would kindly save all of the selected items. But for items that were not selected by the user, not they are mixed up with the new differences. So user have to remember, that this particular item he did not select intentinally, but this item that is not selected is a…

    8 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. resize column widths on "deployment history" page (no truncated values)

    On the deployment history page, the column widths are fixed. If you have a value in the "friendly name" column that's over a certain character count, it gets truncated automatically. there is a tool tip to see the full value by hovering, but if you use consistent naming standards for naming deployment packages, this can result in having to hover over many package (i.e. rows) to find the one you want.

    if making the column width customizable isn't possible, then making the "friendly name" column character limit longer would be a good start!

    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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow upload of Scratch Org Definition file from VCS

    On the "Create a new scratch org" page -- since SFDC recommends that Scratch Org definition files go in VCS (see https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm)

    then the Upload dialog should offer an option to browse repo/branch/folder for the desired Scratch Org Definition file (default path would be main/config)

    and, once selected, the other portions of the page that are overridden by the Scratch Org definition file should be both populated and disabled so the user gets a confirmatory echoing of choosing the right scratch org definition file

    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

  6. Restore specific Salesforce files from backup

    From the user interface, allow a backup user to select and restore a specific file from a backup job.

    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  ·  Data backup  ·  Flag idea as inappropriate…  ·  Admin →
  7. Retain Deployment Friendly Name and Notes After Failed Deployment

    When attempting to validate a deployment, and the validation fails, Gearset retains the deployment's friendly name and notes fields from the validation. The user can make any necessary changes to the deployment, and won't have to re-type this information when attempting it a second or third time.

    I'd like to see this same functionality when dealing with a failed deployment that doesn't use validation. Validating a package takes two steps (long steps), and typically I only want to use this option when delaying a deployment. However I often use it anyway just so I can retain my data in these…

    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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Repo cleaner for managed package deletions

    When you delete a managed package from VCS by deleting its <InstalledPackage>, Gearset should look for all traces of that managed package in VCS and delete those files/update the metadata

    The <InstalledPackage> file identifies the namespace - eg. SomePkg, and Gearset should be able to remove files that start SomePkg__ as well as delete/edit metadatablocks within other files that reference SomePkg__c.

    It is extremely tedious to remove managed package metadata from VCS otherwise; especially if the customer opted to put a lot of managed package metadata in VCS (perhaps by accident)

    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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow users to share deployment drafts across different Gearset environment

    Lets say multiple vendors are working on different environments and done the deployment across all the lower environments using their own Gearset. But coming to the production org. internal team will be performing the deployments using internal Gearset. So Instead of recreating the deployment draft again, it would be very useful internal team can reuse the draft created by vendor in different Gearset environment.

    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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  10. Mass deletion of data from backup

    We want to know how to automate the deletion in backup system.

    Common use case is deletion of customer data due to legal compliance.

    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  ·  Data backup  ·  Flag idea as inappropriate…  ·  Admin →
  11. Choose Delete action per Metadata Type for CI jobs

    In the past we had troubles deploying reports via CI, they were not showing/deploying, the workaround was to enable the filter to include all reports. This works to solve that, but now I am looking at including more into the repo and start using delete actions in the CI jobs as well. The downside is that because we have to have all reports in the filter, the CI job will delete reports created by users in non-private folders. A freedom we want to give certain users in Production.

    What would be an epic enhancement (and solve this challenge) is if…

    25 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 →
  12. "Dismiss/Hide Item" option for any found comparison

    There are numerous "changes' that aren't actually changes (ex: logo images, Global Picklist set order). It'd be great to hide those those changes or dismiss them in a comparison to not look at them. Once it's dismissed, it's out of sight and there is no need to evaluate it every time you look at a saved comparison. It'd be clear that it was evaluated and not dismissed.

    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 →
  13. Allow 'OR' combination for multiple External ID's in Upsert operation

    Gearset allows the selection of multiple External ID's in an Upsert operation as part of a Data Deployment.

    However, the system implements an 'AND' combination across all the external ID's specified on the object.
    Effectively, ALL external ID's need to be present on the target side for the match to be identified and record upserted. If all external ID's are not present, the system performs an Insert on the target org.

    Please allow an 'OR' combination across multiple External ID's. Arguably, this should be the default option, but at the very least, a user needs the ability to decide how…

    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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Filter option: not containing, eg. rather than filtering for 'custom field', filter by components not a 'custom field'

    A better example might be I don't want to see anything that has the word 'contact'.

    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 →
  15. Ability to differentiate between scheduled metadata deployments from validated packages and non validated packages

    Under Deployment History

    1. All scheduled packages should appear. This is not the case today, validated packages that have been scheduled appear under validated packages with a Scheduled Date but not under Deployment History

    2. Scheduled packages should have a link to the appropriate Validated package if any.

    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 →
  16. Option to ignore: <personAccountDefault> in XML

    When comparing XML for RecordType permissions in Profiles, some Sandboxes return:
    <personAccountDefault>true</personAccountDefault>

    As part of the XML, even though person accounts are not enabled, this makes comparing annoying.

    It would be nice to have an option to ignore this.

    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

  17. Allow serial deployment instead of parallel

    When executing a data deployment, an 'Unable to lock row' error can occur if multiple transactions try to lock the same record in Salesforce.
    Because the batches are executed parallel, the chances of getting this error high, depending on the situation.
    For example the master record in a master:detail relationship will always get locked when a DML is executed on the child record.
    If two batches are executed at the same time and they both have at least 1 record that references the same parent, then a locking error will occur.

    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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Warn on Master/Detail deployment even without comparing Custom Fields

    If you compare Custom Fields and try to deploy something in an Object that is in a Master/Detail relationship without including the Lookup field, Gearset will warn you that the deployment will fail.

    However, if you don't include "Custom Fields" in the comparison, (for example just comparing Validations) and try to push it, you will hit an error:

    "Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field"

    Gearset could easily warn the user on this when trying to push a Validation Rule on a MasterDetail object, even if Custom Field was not added to the comparison.

    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

  19. create a Default Value setting on Source Control & Connections

    Reading the previous suggestions this might be a bug.

    Where a user has multiple connections to Github, Bitbucket etc. It would be good to be able to set a default connection.

    It is suggested that when you go to Compare, the last selection should be displayed. But I am not seeing that happening?

    I would expect the default Source to display, no matter what Compare I and setting.

    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  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  20. add an account based autonumber field to deployment that could be used as a friendly reference

    This could be automatically prefixed to friendly name of the deployment.

    Sth like "000035"

    Could be a simple counter (that I see you have implemented "This is your NNth deployment...").

    If the autonumber would pop up automatically then I would not need to figure out a reference and type it myself.

    Currently, info that potentially could be used: datetime (too long) , url (way too long)

    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 →
  • Don't see your idea?

Feedback and Knowledge Base