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. Gearset API to externally trigger Gearset actions

    It would be incredibly helpful to trigger Gearset comparisons, validations, deployments, etc. from an external source using an API. Our team uses GitHub for our VCS, which provides the perfect opportunity to:
    1. design webhooks to validate changes in order to approve a Pull Request
    2. design webhooks to automatically deploy changes to an org once the PR is approved.

    Additionally, CI tools such as Jenkins, TravisCI, TeamCity, etc could use such an API to design complex builds that still employ Gearset, but use the external tool for additional actions outside of what Gearset provides for their CI features.

    90 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. Provide the option to ignore whitespace differences in Apex

    It would be great to have more control over the diff process - particularly to be able to ignore whitespace changes.

    If I've made an actual function change to a class, and also auto-indented it, then it would be a lot easier to see the important change if I could hide the whitespace-only changes.

    Having the ability to suppress whitespace-only changes on the list of changed objects would be really useful, too.

    53 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. Provide individual class code coverage statistics

    Running tests displays overall org code coverage... it would be cool if you could provide individual class code coverage statistics as well, so we could get a good idea of what classes / triggers need attention

    49 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Testing  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add an auto-save feature while building deployment packages

    As Gearset is run through a web browser, if the browser happens to freeze while a package is being built, you don't have the opportunity to save it as a Draft Deployment. An auto-save feature would allow someone to pick up where they left off, or when the last auto-save was done, without having to start from scratch.

    41 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  5. configure which problem analyzer results to use in CI jobs

    Being able to configure which problem analyser results to use in CI jobs.

    For instance, we can’t deploy any changes to managed packages because the problem analyser will ignore them (even though we have components from a managed package that we can modify and deploy without issues), that would help to reduce our manual steps during deployments.

    40 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add merge functionality to the diff tool

    Extend the diff tool to allow the user to perform a merge, creating a new version of the component that contains some changes from the source version and some changes from the target version. This would be very useful in a team development scenario where multiple devs are working on features in individual dev sandboxes and then pushing completed features into an integration sandbox.

    40 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  7. Naming Org Pairs

    I'd like to be able to name 'Pairs' of orgs so I don't have to re-select them, like 'DEV to UAT' or 'HOTFIX to Production'

    39 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Started  ·  7 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  8. Commit-by-commit deployment

    As you are giving an option to trigger the CI job based on repository commit, it would make more sense to only compare the source and target based on the commit items and consider the commit changes for deployment based on your selection of either new, modified or deleted and the comparison filter(which can be optional in this case).

    This will help in reducing the chances of overriding the changes of other teams working in a shared environment or an environment not in sync with the branch.

    There can be other scenarios where we maintain managed package items in the…

    38 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  9. Inline Editing of metadata

    Inline Editing of metadata
    In order to make our deployment successful we had to download the package, modify the version numbers on the flow definitions, and then compare the local package to the target org. It would be very helpful if we can edit the metadata XML in the UI so we can fix the version numbers.

    32 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support package.xml filtering when using Git comparison with a SFDX folder structure

    When using a git repo with a SFDX folder structure + package/xml (in the /manifest folder) gearset dos not take into account elements in the package.xml when checking the option (filter with package.xml)

    32 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  11. Refresh specific item in comparison through context menu

    It would be great to refresh a specific item within a comparison that I know has changed since the last comparison.

    31 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. create an option to have chained deployments

    create an option to have chained deployments so complex deployments can be broken down and sequentially deployed or slaves can be ran

    allowing for multi staged deployments under one CI job

    26 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  13. Introduce 'ListView' as an option in 'Metadata filter' tab

    When navigating to the 'Metadata filter' tab to select filters, there are currently 122 options, however 'List View' is not one of them.
    When navigating 'Metadata Types & Components' in Workbench, 'ListView' is described independently, and I have used it previously when deploying via ANT. Therefore I would imagine there is a way to identify List Views independently of 'Custom Objects'.
    This would be a huge help with a Production monitoring job, as I do not mind if List Views are updated by certain users in Production, but currently they are flagged as differences. Basically, I want to ignore them…

    26 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow source metadata to be customised prior to deployment

    In order to support a development pipeline (e.g. Dev Environment -> Staging Environment -> Production) allow Metadata from the source Org to be modified before deployment to the target Org.

    e.g. I have a RemoteSiteSetting in source that points at https://dev.example.com and in my staging environment I need this to point to https://stg.example.com

    26 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    As part of our ongoing roamdap prioritisation, we’ve decided to postpone work on this feature. This isn’t to say we’re not going to do it at all, it’s just that it’s not on our currently active backlog. If you think we should rejig our priorities please let us know – we’re always adjusting based on customer feedback.

  15. Refresh Comparison should have an option: "Selected Files only"

    A common use case is:
    1. Compare default(66) source and target
    2. Select some files
    3. Deploy
    4. Get some error indicative of either missing file or out-of-date file(s)
    5. Fix file(s) in underlying org/source branch.
    6. "Back to results" Optionally mark additional files as selected.
    7. "Refresh Comparison"

    This takes too long, you just want the selected files to compare (and really, just get on with deploying). You don't want to wait for both source and target metadata to load and compare. You don't want to uncheck/check specific metadata components that represent your selected files. You just want a…

    25 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  16. Stop the reordering of XML when deploying to git

    At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.

    22 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  17. Create Change set without comparison

    Allow user to directly create a change set without doing the comparison. If user has a list of items that needs to be migrated then allow the user to add items and skip comparison step.

    21 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow editing on source XML

    Is possible to snip out parts of a source XML file during a compare and deploy run?

    I have a file that's changed in both orgs and I just want to import the new bits from one org into the other, rather than delete what's new in that second org.

    21 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  19. Ability to chose multiple targets for a deployment

    It would be nice to be able to deploy to multiple environments all at once from one source.

    21 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  20. A configuration to prevent deployment from certain Sandbox Org into Production org

    In most of Tech industry deployment lifecycle, all code or config changes are ideally pushed into production only from a FullCopy Sandbox(Commonly Known as Staging Environment).

    It would be very good to have a feature in GearSet App which if enabled shouldn't allow user deploying data from Dev/DevPro/Partial Sandbox into Production Org.

    20 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 30 31
  • Don't see your idea?

Feedback and Knowledge Base