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. Ability to recreate a reusable list or group for Deployment notifications

    Every week we have a larger sized scheduled deployment for logic updates that runs after business hours. There's usually the same 2-6 people (often increasing) that want to receive an email and/or text message when the deployment succeeds. Whoever schedules the deployment has to add each one manually every time, and it would be nice to have a way to send notifications to a predefined list or group of email addresses and/or phone numbers.

    It usually has to be the person that schedules the deployment, because if someone goes back to add their own email or phone to an already…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  2. Expose Salesforce Validation Errors within Github PR

    Currently when a PR Validation fails (Deploy CI Job with Validate Target setting turned on), the user can click the Gearset "Details" link to go into Gearset to see the exact error.

    Many of our devs use VS Code and Github for their daily work and only rely on Gearset for the CI job. Having them jump into Gearset just to see the error is time consuming and not very intuitive for them. Sure we can find the same errors within the target org of the CI, but at that point the list of validations is large and it's hard…

    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

  3. Allow retention policies to be set on individual core objects

    It would be useful to be able to set individual retention policies on core objects, rather than on the entire backup job. This is for an old org (c.10 years), ideally you'd be able to set differing retention policies on different objects; e.g accounts after 7 years but contacts after 5 years.

    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  ·  Data backup  ·  Flag idea as inappropriate…  ·  Admin →
  4. Trigger a Gearset CI deployment from an Azure DevOps release approval event

    Right now Gearset supports the set up of webhooks into azure devops which trigger deployments when a branch is updated.

    I'm looking for an extension to that feature to also include "approval completed" steps. These are already available to hook into within Azure DevOps, so I'm hoping it'd should be a relatively small piece of work to extend GS to support 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

  5. Increase the size of the 'Create new branch from...' modal.

    When creating a new branch from the 'Create new branch from...' model, it's hard because of the small size of the modal/dialog. Just sizing the modal/dialog larger would make it easier to work with.

    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. Make "Hide Reodering" global switch

    Please add a feature to have globally selected "Hide Reordering" and also hide those files that have no changes after reordering from Changed Items?

    Clicking that on every file to see that there are no real differences is time consuming and slow down the comparison process.

    Scenario:
    1. I am comparing two sandboxes develop with my private sandbox to align with changes made on develop.
    2. I have comparison with many Global Value Sets, Custom fields which are Picklists, flows etc.
    3. Most of them are not changed but are listed as changes. I need to click on each metadata…

    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

  7. Add an option to ignore location changes for Flow

    Hi, when reviewing changes for flows that are being deployed, it would be great to have a toggle option to hide or alternately color location changes which are just the location of elements on the flow canvas editor.
    <locationX>1353</locationX>
    <locationY>1305</locationY>

    Sometimes there are hundreds of location changes and it obscures the important information about what else changed.

    16 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. Ability to mark certain branches as your favorite branch so you can pick them quickly

    When selecting a branch from source control, it would be great if Gearset had an ability to mark certain branches as favorites so they appear the top of branch selection dropdown.

    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. Add the ability to run the problem analyzer while on the comparison screen

    I originally was going to request the ability to append the items found in problem analyzer to the list of selected components, when going back to view the comparison, but then I thought why not take it one step further, and move the problem analyzer feature to the comparison screen? Then, the items it finds/suggests, the user can add them to the package there, or choose to ignore them.

    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

  10. add the option to either hide source control locations where you do not have a connection, or allow a default SCM connection to be selected.

    We only use on source control service, so having to select 'Azure DevOps' before being able to select the repo/branch, is a small step that adds up over time.

    Being able to either hide services that you do not already have a connection for, or being able to default to a service, with the ability yo navigate back up and over, as needed. would be welcomed.

    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

  11. Add or ignore parts of XML after the comparison to ignore other users changes

    If there are multiple users making changing the metadata in Salesforce and when one has to deploy their changes, it is not possible to pick the changes that are specific to one person, For this we have to go to VS code and use git patch mode to add only the necessary changes for a specific user. If we have an option to edit the xml after the comparision and pick only necessary pieces and deploy it to next org will save time and also switching between multiple orgs. Currently the comparison editor is read only mode.

    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

  12. CI Deployment on a Schedule

    We would love to schedule a deployment from GitHub source to a few sandboxes at the end of each 2-week sprint.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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.

    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

    3 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add an Undo Action/Functionality in the Comparison UI

    Add an Undo button to the comparison UI in case someone accidentally de-selects a component from the Selected Items tab. It would save time rather than having re-search for the component and lose your train of thought. You have this feature in Google Docs and sheets.

    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

  15. Select All Option in Deployment history

    It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.

    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

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  16. Record/file level filters for Backup jobs

    Allow Backup job filters to be configured for specific records/files rather than entire objects.

    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 →
  17. Offer option to auto-limit items in clone comparison

    When a deployment is completed, you have an option to clone that package. For many of my deployments, I want to push a package to source control, and then on to production. The second comparison could be limited to just the items in the cloned package. Would be great to have an option to limit second comparison to only the meta-data items in the clone. Would allow subsequent comparisons to run much more quickly, if the user is confident that the package has everything needed for that specific 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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  18. API to export backup to S3 for data warehousing/datalake

    A lot of time we would like to have data out of SF not just for backup purposes but for data analytical purposes as well. Ownbackup currently has this functionality via APIs.

    https://documenter.getpostman.com/view/12146739/TzJuAxgY#0f1fc918-7616-4b58-8d52-0e8370f57d9b

    https://ownbackup-kb.magentrixcloud.com/articles/knowledgebase/Using-the-OwnBackup-API-5-6-2020

    If gearset has this, it would help us move to GS for all our SF problesms

    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 →
  19. Option to ignore all package differences in Apex classes

    Our Apex Classes reference managed packages that are updated automatically in our sandbox/production environments. This causes many classes to get picked up unnecessarily in our comparisons/CI deployments.

    Unlike https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/43917792-add-an-option-to-ignore-package-version-difference this is specifically for different package namespaces between the source and target.

    In this example the source has one namespace and the target has 2 package namespaces.

    It would be very useful to be able to choose to ignore all package differences in comparisons and 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

  20. Filters

    Edit "Existing Saved Filters" on an "Existing CI Job"

    If using a saved filter on CI job, there is no easy to update an existing saved filter from the CI job directly.

    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

    1 comment  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 41 42
  • Don't see your idea?

Feedback and Knowledge Base