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.

  1. 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'

    3 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  Improvement  ·  Admin →

      Thanks for the suggestion. We can definitely look into this.

      Would you expect to create these pairs from the compare screen, or the manage orgs screen?

      Thanks,
      Jason.

    • Email notification for failed deployments

      Getting an email when a deployment succeeds is nice, but it would be nice for failed deployments too. (Unless maybe I've missed an option for this?)

      2 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

        3 comments  ·  Improvement  ·  Admin →

        We’re planning to improve our reporting and notifications in the coming months. We’ll definitely consider adding in failures for manual deployments to that list of improvements.

        I’ll post an update when we’ve got a more concrete plan on the changes we’re going to make.

      • 1 vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

          2 comments  ·  Bug  ·  Admin →

          These failures appear to be down to intermittent Salesforce errors when running test jobs. We’re investigating the cause, but it’s proving to be difficult to reliably reproduce.

          Do you have any orgs/jobs for which this repeatedly happens, or is it seemingly random?

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

          3 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            1 comment  ·  New feature  ·  Admin →

            Thanks for the suggestion.

            We have plans to improve the way the diff viewer handles changes and whitespace in the future, though it’s not currently under development.

            Thanks,
            Jason.

          • 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

            2 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

              0 comments  ·  Improvement  ·  Admin →
            • "Changed on" date on source control side of comparison does not show

              We have no way of knowing when the files were last changed on the source control side. Tried only with BitBucket though.

              1 vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)

                We’ll send you updates on this idea

                1 comment  ·  Bug  ·  Admin →
              • Send a link to the report in the notification

                It'd be nice to have a link to the report included in the notification for any scheduled monitoring, test run or deployment/validation.

                1 vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  2 comments  ·  Improvement  ·  Admin →

                  Thanks for the suggestion.

                  When you run a deployment, the deployment success email contains the PDF of the deployment report, as well as a link to your deployment history to view the full information.

                  For the test/change monitoring emails, what sort of report would you like to see? Would you like to see the full information on tests run or just a summary of key stats?

                  We don’t currently provide the ability to export PDF reports for our change and test monitoring jobs in the same way as our deployments, but it’s something we’ve been thinking about putting in.

                  Thanks,
                  Jason.

                • 1 vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    1 comment  ·  Improvement  ·  Admin →

                    HI Celio,

                    Thanks for the suggestion.

                    Could you explain a little more about the primary reason for wanting to store these failures?

                    Where would you expect these results to be stored – in a separate tab in the history set, or alongside the other deployments in your history?

                    We currently store failed scheduled deployments in your validated package history. We can certainly look at whether we could expand this to cover manually started deployments as well.

                    The reason behind our initial decision not to store these in the app is that the user would be using Gearset at the time of the failure, so we would prompt them to fix the deployment then and there. Our draft deployment feature, which allows you to save and build packages over time, might also help to work around this requirement for you?

                    Thanks,
                    Jason.

                  • Provide option to disable parallel apex testing in Scheduled Tests

                    Scheduled Test runs can fail due to UNABLE_TO_LOCK_ROW errors. This is due to what amounts to a bug in SF: accessing public custom settings in tests which are run in parallel can cause deadlocks. Really, the tests ought to be isolated from each other, but they are not. See:

                    https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_best_practices.htm

                    The workaround in SF is to disable parallel apex testing.

                    If Gearset could do that during the scheduled test run, it would prevent false test failures.

                    I guess I could change the option on the SF org, but sometimes parallel testing is useful, so I wouldn't want to disable it…

                    1 vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      Under review  ·  0 comments  ·  Improvement  ·  Admin →
                    • Allow Source Metadata To Be Customised Prior To Deployment To Target

                      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

                      1 vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        0 comments  ·  New feature  ·  Admin →

                        Thanks for the suggestion Paul.

                        It’s something we should be able to do, but we need to do a little bit of investigation first to work out exactly how this feature should look and what the functionality would be.

                        Thanks,
                        Jason.

                      • Show more info on source control on comparison screen

                        Would be nice to see something like "SOURCE: repo_name, branch_name (username)" when comparing with a repository.

                        1 vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          0 comments  ·  Improvement  ·  Admin →
                        • Add ability to exclude specific files/folders of repo from a compare with source control

                          Currently, if you try to compare a repository to a Salesforce org, it will throw an error with only the ability to send a report to Gearset if the repository contains files that are not compatible (gulp files, package.json, etc. at the root of the repo or any folder that isn't corresponding to a Salesforce type of file).

                          My suggestion would be to add the ability for the user to exclude those files or folders from the compare and retry when it fails. This issue currently prevents us to use source control in the comparisons.

                          1 vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  Improvement  ·  Admin →
                          • Org metadata snapshots

                            Allow a snapshot/backup of an org prior to running a deployment. Allow us to use this as a source of a new deployment if we want to revert any changes previously deployed, or at least download the package.

                            4 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              0 comments  ·  New feature  ·  Admin →

                              Posting an update on this as we’re now into Q3.

                              This is still on our roadmap to add as an explicit feature, likely to come out in Q4.

                              The reason for the pushback on snapshots is we think that the recently released deployment rollback (https://gearset.com/blog/rolling-back-unwanted-changes-in-a-salesforce-deployment) feature provides much of the functionality people wanted with snapshots – to be able to roll an org back to a pre-deployment state.

                              We realise this doesn’t cover every need, so are planning to release on-demand snapshots as well in the coming months. Please get in touch if you have any feedback on rollback/snapshots that’d you like to seem implemented and we’ll see what we can do.

                              Thanks,
                              Jason.

                            • Allow users to choose when change monitoring and unit testing jobs run

                              The change & test automation is great, but we can't choose when these jobs run. The option to choose when to run jobs so they don't coincide with dev work would be a great addition.

                              3 votes
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                0 comments  ·  Improvement  ·  Admin →
                              • disable changes due to white space tabs

                                Create a way to turn off diff that are caused by spaces, tabs, and returns.

                                2 votes
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                • Show which tests have been run

                                  In the post-deployment summary, rather than just list the numbers, list the actual tests that have run.

                                  1 vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    We’ll look into how we could add this without making the interface too difficult to dive into. In the meantime, our new unit testing automation feature may be of interest – it allows you to automate unit tests and see exactly which have passed and failed.

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

                                    5 votes
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                    • Don't see your idea?

                                    Help us improve Gearset

                                    Feedback and Knowledge Base