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.

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
  1. Allow Monitoring Jobs on Source Code Repositories

    Currently, Enterprise users can create monitoring jobs on sandboxes, so that they may be notified when a sandbox's metadata changes. It'd be great to be able to perform the same monitoring action against source code repositories (GitHub!).

    An example use case would be detecting when undesired metadata types enter into the repository. This is important because CI jobs will fail on certain metadata types, so we want to ensure that they never make it into source to begin with. Additionally, our business has decided that some metadata types should never be captured into source.

    7 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

    • When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist

      When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.

      4 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        0 comments  ·  Bug  ·  Admin →
      • Allow for custom metadata permissions to be included with a single click when custom fields are being deployed

        For example; when adding new custom fields, you generally have to add the permissions as an additional line item to the deployment. Having a checkbox or something that will have gearset automatically add the permissions associated with the metadata currently in the deployment list would speed up the process. Users should also be allowed to deselect lines that were automatically added.

        4 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  New feature  ·  Admin →
        • 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.

          16 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

          • Allow us to configure a push notification when comparisons are done.

            It would be great if we could configure a notification when a comparison completes. Sometimes comparisons take a long time!

            3 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              0 comments  ·  New feature  ·  Admin →
            • Add a "Clone package" button to the Deployment Results page

              My workflow is currently to deploy a change, browse to the deployment history to find my deployment, and immediately clone the deployment for another environment. It would be really nice if the clone button were available upon a successful deployment.

              5 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                0 comments  ·  New feature  ·  Admin →
              • Upgrade to PMD 6

                PMD 6 includes useful stuff like allowing annotations in the code to suppress warnings. It would be great to be on that version.

                Stephen told me via the support chat that it wasn't simple to just upgrade, so I thought I would submit it as a feature request.

                2 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                • Allows admins to limit the available branches of a repository

                  When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.

                  3 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                  • 2 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                    • Create the ability to migrate components to new source and target orgs after having in a Saved Drafts.

                      When saving components into drafts, when validated, we would like the ability to be able to migrate the same components into new source and target orgs.

                      7 votes
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                      • Ability to add custom trigger points to trigger CI from source control

                        At the moment the tool allows you to only kick off CI jobs when a branch is updated.
                        This is actually limiting the capability of the tool in itself,
                        because services like Bitbucket allows you customize trigger points, as to when they should ping the webhook;
                        such as the creation of pull request, merging a pull request.

                        The two trigger points mentioned above are specifically very important because you would want to run validation CI jobs on the creation of pull request or when the merge completes so that you can actually ascertain if your branch compiles.

                        Based on an…

                        2 votes
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                        • Trust Site

                          Right now, Gearset is down and we cannot use it. It would be good to have a trust.gearset.com site that shows what is going on and what the team does to fix the issue...

                          1 vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                          • Allow editing all CI Job Fields

                            One should be able to edit all the fields on a CI Job, especially the source and destination fields.

                            2 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                            • Avoid spurious Analyzer message when deploying external objects (e.g. Foo__x)

                              If you create a new org, add an External Data Source, add External Objects, and deploy to a target (source control), you will get this spurious analyzer message:

                              "Some standard object fields which don't exist in the target organization are being deployed, which indicates they might use features not enabled in the target. You need to remove these from the deployment, otherwise it's likely to fail."

                              and all your external objects are enumerated, e.g.

                              Orders__x
                              Customers__x
                              ...

                              These are not standard objects, and, as they are new, would of course not be in the target. Analyzer is being too "discerning"

                              1 vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                              • When creating a scratch org, allow a user to define the expiration number of days

                                Currently, when creating scratch orgs, the system automatically sets the expiration to seven days. However, scratch orgs can last as long as 30 days. Would it be possible to define the expiration number of days during creation?

                                1 vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  0 comments  ·  New feature  ·  Admin →
                                • Ability to change the value of a field on import

                                  Price Rules have Price Conditions and Price Actions and sometimes Lookup Queries hanging off of them as related objects. Some of the price rules wouldn't get created because there is a field called Conditions Met and it equaled Custom. If we were doing this migration via data loader, I would set those records to equal All for the value just to get the price rules in. Then we would load the Price Conditions. Then we would do an update to the price rules to set it to what it should be - Custom. We cannot save the record initially with…

                                  1 vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    0 comments  ·  Data  ·  Admin →
                                  • Build Comparison Manifest from pull request

                                    It would be cool if the custom deployment configuration could be driven from a Pull Request . For example, in GitHub, the Pull Request knows which files were changed and approved. Why not use that list to instantly populate a comparison to create a deployable manifest to go from source control to org?

                                    1 vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      0 comments  ·  New feature  ·  Admin →
                                    • Indicate whether a Validated Package is enabled for Quick Deploy

                                      T0 - You Validate a package to PROD (run all tests)

                                      T1 - You or someone else does a deployment of something else, no matter how minor, to PROD.

                                      T2 - You click Deploy of the Validated Package from T0, all the apex tests are rerun. This is by design per SFDC yet Gearset doesn't tell you in advance that Quick Deploy is not available. Something you think will take a couple of minutes now takes 30 minutes or more. You think you screwed up or Gearset is broken

                                      Suggestion: On Validated Packages page and on the page of a…

                                      2 votes
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        0 comments  ·  New feature  ·  Admin →
                                      • Skip CI Jobs to source control when there are no changes.

                                        After setting up a CI job from a Salesforce sandbox to a Bitbucket repo, it looks like the CI job always runs a commit, even if there are no actual changes. It would be great to not have this happen to avoid having many commits where there are no actual changes.

                                        5 votes
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                        • Friendly name and details should also clone and pre-populate once you clone a deployment or at least have an option to

                                          In my eyes, this is a bug. When we clone a deployment, we have to copy and paste the friendly name and details into the new one. Most times we're performing a clone, it's when we're just moving to a new environment. We typically go from sandbox to staging and then sandbox to production after the changes have gone through QA and UAT. We deploy from the original location to mitigate problems.

                                          You could ultimately change your deployment processes to where a deployment is a record that can be open or closed. If it's open, you can change the source…

                                          2 votes
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                            0 comments  ·  Bug  ·  Admin →
                                          ← Previous 1 3 4 5 11 12
                                          • Don't see your idea?

                                          Feedback and Knowledge Base