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.

I suggest you...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

369 results found

  1. Ability to Name a Backup Run

    It would be great if you could name a backup run.

    Sometimes when backing up its handy to label in in case it was done for example before a deployment or large data load. Then this can be identified in the future or to refer back to it. Otherwise you need to remember the date and times! :)

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Data backup  ·  Admin →

  2. Offer Canadian data residency.

    We have clients in Canada that require data residency for data backups/deployments and even metadata deployments/processing.

    Please add the option for a Canadian hosted Gearset account.

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Admin →

  3. Populate Pull Request Templates from git providers

    When creating a pull request directly in Gearset, it would be ideal to pull in the existing templates defined in BitBucket or GitHub.

    A middle of the road solution (if GiHub or BitBucket's API doesn't support this) could be defining a pull request template in Gearset.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  2 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →

  4. 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)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  2 comments  ·  Deployment automation  ·  Admin →

  5. 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.

    Here is my current workflow:

    Start a new compare and edit / save the filter from there, then going back to the CI job, refreshing filters and reselected the saved filtered.

    If multiple CI jobs are setup it's easy to miss some jobs which are dependent on updated filter.

    Alternative solution - Provide toggle to update all related CI jobs which use the filter.

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Admin →

  6. Option to sort Custom Application XML

    While this can be done with VSC custom plugins for SFDX, I think it would be really beneficial if Gearset offered the ability to sort Custom App XML in comparisons in order to see what's actually changing between a source and target for lightning page activations. Due to the way SFDC generates this XML, the way page activations are ordered is very difficult to follow, and I think it's an opportunity to make that easier especially for declarative config users of Salesforce.

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  4 comments  ·  Comparisons and difference visualization  ·  Admin →

  7. 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)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Data backup  ·  Admin →

  8. Add an option to ignore package version differences in Apex classes

    I see many differences between apex classes where the only difference is the package version(s), no difference in the code itself. It would be nice to have an option to filter these out so that only the apex classes are shown where the code is different.

    17 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Admin →

  9. Create GitHub App as alternative to GitHub OAuth

    Gearset currently uses OAuth to connect to GitHub, and the way that works is that the OAuth connections have permissions to all repositories that my user has access to, which from a security perspective is a problem, because if the github key were ever compromised, it would provide very broad access to customers GitHub organizations.

    Security teams would feel much better with the ability to limit the scope of access to just one repo instead of all the repos that my GitHub user has access to, which can be accomplished by creating a Github App which can be installed for…

    10 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →

  10. Gearset silently removes SocialPost Layout Permission when deploying

    When deploying from one org to a git repo (or other org) and selecting Layout + Profiles gearset will display a Layout Permission for the "SocialPost" object. However when completing the deployment "SocialPost Layout Permission" is removed because deploying it would cause Salesforce validation errors. This is not displayed anywhere and always causes "SocialPost Layout Permission" to show as "New" when doing a comparison.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    This behaviour was converted to a problem analyzer as of July 23rd 2021.


    You should now be able to include these Layout Permissions in your deployment by ignoring the suggestions from the "Items that can't be deployed through the Salesforce metadata API" analyzer

  11. 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…

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  0 comments  ·  Data deployment  ·  Admin →

  12. 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)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Admin →

  13. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Admin →

  14. Desktop notification when deployment is complete

    When you launch a deployment to a target org the browser tab (which will be one of many in your browser) shows Depl...

    Since the user is multi-tasking, it would be helpful to add a desktop notification and change the browser tab to alert user when deployment is done (like what Gearset does when a comparison is completed)

    This could be a D ✅ or D ❌ depending on whether deploy succeeded or failed

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Admin →

  15. Identify that metadata is the same, even if ordered differently by metadata API

    There are a lot of instances where the comparison will identify metadata as different, but the only difference is the way the API is ordering the XML. I've seen it happen a lot with picklist values on multi-select picklist fields. It would be nice to be able to turn this on/off somehow so that metadata that isn't truly different won't show up in the difference compare.

    13 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    7 comments  ·  Comparisons and difference visualization  ·  Admin →

  16. Support org shape parameter for creating Scratch Orgs

    Currently definition files are required for creating scratch orgs but there is no support in GearSet for the use of the sourceOrg parameter as per the sfdx documentation here : https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_shape_scratch_def.htm

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →

  17. Make fail job optional for warning PMD analyses

    As a developer leader, I don't want the job to fail if I get a warning from PMD. But I want to be notified if the code has any warning.
    I would like the failure for warnings to be optional. But always be warned that it has flaws.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Admin →

  18. 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.

    21 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Comparisons and difference visualization  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    The "simply differences" toggle in the comparison grid now hides location changes in flows to make it easier to identify important changes. The location changes are still included when deploying changes to the flow.

  19. Prevent Deployments from Including LiveChatButton with Omni-Channel Routing

    https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_livechatbutton.htm

    LiveChatButton metadata that is routed using OmniChannel is not supported with the Metadata API and the deployment will fail.

    It would be great if Gearset had an analyzer to remove this for end-users to prevent the error.

    The following property is null for LiveChatButtons routed through Omni-Channel

    <routingType xsi:nil="true" />

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Admin →

  20. Search option when selecting a Data template

    When choosing a template in a Data deployment, an option to search all templates is needed. We will be updating/modifying/saving new templates often and a manual scroll will become inconvenient. Control F works to find a template, but a dedicated search option would be preferable

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  0 comments  ·  Data deployment  ·  Admin →
1 3 5 … 18 19
  • Don't see your idea?

Help us improve Gearset

Categories

Feedback and Knowledge Base

(thinking…)