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

223 results found

  1. Remove/Deactivate new feature for batch comparison

    A few weeks ago, Gearset added a new feature to officially make the comparison faster, by showing already results of first batch and add the rest later on.

    This feature makes it much more difficult to do comparisons. First of all, I don't see any benefit. I still need to wait for the whole comparison to finish, because I still need to now, what has changed. Why should I look into the first things, when I need to look into it again, after the rest is compared. So before I can select anything, I need to wait the whole time…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Activity Task Event field level security validation in Profile

    Hi Gearset Team,

    I would like to have a metadata validation for profile field level security involving Activity, Task, Event object as they are related to each other in Salesforce.

    For example:
    If we do a retrieve for Activity, Task, Event object along with profile. In the profile metadata it would specify this:
    <fieldPermissions>
    <editable>true</editable>
    <field>Task.FieldX__c</field>
    <readable>true</readable>
    </fieldPermissions>

    However, if there were to be a mistake in the profile metadata and we commit them in version control it is detected as a 'new item' in Compare and Deploy

    <fieldPermissions>
    <editable>true</editable>
    <field>Activity.FieldX__c</field>
    <readable>true</readable>
    </fieldPermissions>

    When we select this new changes and…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Ignore Business Owner changes between Sandboxes

    This was marked as "Completed" in https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39507649-resolve-data-owner-user-metadata-from-difference

    But really the issue remains.

    When "Business owner" is populated in a field, it will show as "different" since the XML is showing username, which is different between sandboxes.

    This make trying to do comparisons to find differences very challenging.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. comparison between 3 or more ORGs

    i would like to see in a future update about comparing 3 or more Orgs to possibly fine tune checks between production, and multiple sandboxes to make sure everything looks as needed to verify no sandboxes are overlooked for refreshes if needed.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Show "All" Different Items

    Instead of a tab showing 'All Items', even items that are the same, maybe show a tab of All Different Items, which would show New, Deleted, and Changed in a single view without having to sift through the 'All Items' for 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add option to load missing dependeces only.

    Example:
    When I already selected metadata filter with many items, downloaded metadata, compared, checked, and clicked deploy then I am getting an error that some dependency is missing but it is metadata type that wasn't selected previously.

    Currently:
    I need to click refresh comparison select additional metadata types and reload all metadata from both sandboxes. It is very time and resource consuming with big packages.

    As a solution:
    I want to have the possibility to click a button and select on the metadata list only those that I want to add to the current package and only those should be…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Delegate Access by Comparison

    Provide an additional delegate access option: be able to grant this at a comparison level to a user vs at the org level (situation is predominately experienced for Production comparisons/deployments). Granting access at an org level gives too much access (CI jobs, etc) for some users so it would be ideal to have a narrower scope.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Support Email Template Folder metadata migration

    Metadata API for EmailTemplateFolder does not accept wildcards so you have to know the name of the folder to be able to pull it down and migrate it. Currently (as of 2-16) the Gearset product cannot pull these.

    Suggest that they add functionality to make a SOQL call to get all the folder names, at which point they should be able to pull them. Allowing for compare and deployment.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Meta Comparison Filter Based on User and/or Timeframe

    It would be great if there was a way to create a metadata comparison filter, and not just filter with regard to metadata types, but also filter by which user made the change, or the timeframe when the change was made? For instance, it'd be great if I could create a filter based on changes I made within the past 30 days, or a specific timeframe. Filtering by metadata types takes very long for large orgs, even if I reduce the metadata types down to 1 or 2.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Field Dependencies for Reports

    When deprecating a field and replacing it with a new one, we need to be able to see where they are used in all reports, including private folders, which the "Where is this used?" feature does not detail.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Add Comparison Column for "Environment"

    Add a column for "Environment" which signifies which environment the change took place. For instance, this would tell you whether the changes took place in Production Only, Sandbox Only, or both.

    Then, I could filter by Sandbox Only and both to see only the changes I made recently in the sandbox that I need to push to Production. Right now, I have to sift through the many little changes to items that occurred in Production.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Filter Column Sub-Levels

    If I filter a column, it does not apply those filters if I open the sub-levels of an item such as "Depends on" or "Used by". For instance, if I filter OUT under the "Difference Type" column "No Difference," when I search through those sub-levels, it should not show me items that are "No difference."

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. sfdx repo deployment should be in subcomponents

    Context: Compare and Deploy from Org to a Repo.

    as i understand it, even if my repo is in SFDX format (Object subcomponents), Gearset still does the compare in the metadata format.
    it reads the components from sfdx, combines into a .object form, and then applies the changes to the .object file and then decomposes again.

    this is causing unintentional changes to be part of our PR

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Option to ignore package namespaces differences in Apex classes

    Our Apex Classes reference multiple 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 between source control (where the managed packages are not committed) and org.

    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 as a team-wide 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Create new branch using type-forward / auto-complete from JIRA (or other supported tool)

    It would be great if you have JIRA connected, to make it easier to create your branch. So basically type-forward (-ish) functionality to identify a JIRA ticket and take the issue ID and description as branch name.

    Say your JIRA ticket is ISSUE-1234 Implement this awesome feature.

    The default branch name would be issue-1234-implement-this-awesome-feature.

    (Where it reads JIRA could be Azure or any other support tool of course).

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base