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. Missing analyzer - Search Settings - when custom object not in target

    If you deploy Settings | Search there are entries for <searchSettingsByObject> with sub-element <name>myFoo__c</>

    if the target does not include the custom object myFoo__c, Gearset doesn't flag this as a warning with a default fix to exclude the <searchSettingsByObject>

    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  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add Repo Cleaner support to SearchSettings

    When you delete a custom object, the Repo Cleaner should remove the references to that custom object in the Settings metadata type - specifically SearchSettings | <searchSettingsByObject>

    Otherwise, it becomes impossible to deploy Search Settings via CI jobs

    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  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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

  4. Add a filter in monitoring job to exclude changes done by Gearset

    To help identify changes done manually to the org it would be nice to have a filter which excludes all the changes done by Gearset deployment.

    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 →
  5. Improve error message when XML is not properly escaped

    When I choose to compare metadata with my source as my VCS, there was an "&" char in the recordtype XML definition file.

        &lt;values&gt;
    
    &lt;fullName&gt;Food &amp; Beverage&lt;/fullName&gt;
    &lt;default&gt;false&lt;/default&gt;
    &lt;/values&gt;

    This threw an error and there was no support and no explanation at that time.

    I suggest you to improve this error message.
    Message I got:

    Could not parse the XML for 'force-app/main/default/objects/Lead/businessProcesses/Buyer.recordType-meta.xml'. Error occurred at line 71. Further details: An error occurred while parsing EntityName. Line 71, position 29.

    File, line and position it's ok. maybe a link to Gearset docs with walkthrough with this probable cause when a parsing…

    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. Add the ability to order/chain overnight jobs

    Gearset offers various automated jobs that run overnight e.g. Org Monitoring Snapshots, CI Jobs, Unit Test Runs.

    it would be great to be able to set an ordering on how those run for any particular org. For example, a natural order for the night jobs may be:


    1. Monitoring Snapshot

    2. CI run

    3. Unit testing

    This means we have a backup before making any potential CI changes and the unit tests show the results after CI. It would also allow us to make sure that the jobs don't clash.

    Ideally, we'd be able to do this without just specifying exact times to…

    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 →
  7. Delete comparisons

    Be able to delete a comparison run with wrong filters or just keep the latest 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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…

    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 →
  9. 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 →
  10. Reuse earlier retrieved metadata, if nothing has changed

    We have a large org and need to select many filters. A comparison take ages. Source of our deployments is mostly Git, which is very fast in retrieving metadata. I would like to have an option, to assume that nothing has changed in target and skip loading metadata of that org and use the metadata of an earlier comparison.
    If we have a small bug in our Git (e.g, test class not correct), we get an error while deployment. That's okay. We fix it in about 1min and want to deploy again. Loading metadata from Git is instant finished loading…

    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 →
  11. Add the concept of Master seeding object

    One great feature to have, would be the possibility to identify a Master object from which the filters applied on it would be applied on all dependent objects automatically.

    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 →
  12. Delta only validation CI jobs

    Idea is to have the Delta CI for Validation only Job, so the as well, so the validation process will become faster .

    The option of validating a PR in the deployment job does the same task, but is comparing too many items of metadata and it is taking too long.

    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 →
  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…

    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 →
  14. Deactivate email deliverability on Data Deployment

    User email are masked in Sandboxes and we can mask Contact emails as part of the data deployment. This still leaves the Org Wide addresses as valid emails. If there is automation that is generating emails related to the data that is loaded, they will be delivered to the Org Wide Addresses.

    It would be useful if the same script that is deactivating validation rules could set email deliverability to systems emails at the same time.

    In the even that email deliverability was set to all emails in the Sandbox and not adjusted before the data deployment we would have…

    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 →
  15. Update Metadata Change Monitor Report

    When you update the change monitor report metadata filters and include new metadata types, the next monitor report shows all the newly added metadata as "New Items" on the report. Although not a big deal it did cause an alarm for us not realizing it was due to the change we made prior. It would be a "nice to have" feature if either you don't include the newly added metadata types as "New Items" on the initial report or flag them and have a visible cue to indicate the items were a result of newly added metadata items on the…

    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 →
  16. Show deployment friendly name on Deployment successful page

    On the "Deployment successful" page, I'd like to see the Deployment friendly name displayed. This would be much more useful than the Salesforce Id that is currently displayed.

    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 →
  17. Force selection of fields to use instead of selecting id as default

    In the select related objects page, Gearset selects id as the 'fields to use' field. If we are deploying a large set of data and by mistake do not change the 'fields to use' field then we end up creating duplicate records for Upserts. Would be great if there is an option to enable or disable the default selection.

    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. For failed CI job runs, develop a way update to the job status

    When for whatever reason, jobs can get job stuck in status "Deploying".

    The real deployment task is already successfully finished in the org, so I would expect that the status of the CI job would be "Succeeded".

    I was assured that in 24hrs the status of the job will automatically reset, but can we have also a way to force an update to the CI job manually?

    Note: The "Cancel running CI job" button is visible and clickable, but doesn't do anything with this stuck CI 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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  19. Preview of records for data deployment

    It would be great either via the UI or a downloadable file/CSV, if we could see all the records that will be migrated in the data deployment. We're able to see the list of successful or failed records after the fact, it'd be nice to see the list of proposed records before hand. This would help identify if we're in the correct ballpark, say 500 records vs. 5000, and not knowing that until after the deployment gets attempted.

    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 →
  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)

    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 →
← Previous 1 3 4 5 36 37
  • Don't see your idea?

Feedback and Knowledge Base