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

1176 results found

  1. Scroll to top of category, when switch between All Items, Changed Items etc

    Just a user preference item – when you switch tabs (ex: New Objects to Deleted Objects), it doesn’t place you at the top of the window.

    So if I scroll down through all the New Objects and then switch tabs to the Deleted Objects, it just places me in the same relative location as I was in the New Objects tab.

    It would be nice to have it reset to the top of each window when I switch tabs.

    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)
  2. Here's the best solution: Be able to quickly select the custom objects and standard object custom fields AND only the related metadata items

    Would like to be able to quickly select the custom objects and standard object custom fields AND only the related metadata items to make then function correctly (permissions, layouts, field level security, etc..)

    Then we could go back and migrate all the process automation stuff - workflow rules, flows, trigger, etc..

    It always starts with the data schema first. We need a quick way to see what is different between two orgs and get that synced first

    7 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)
  3. Unselect all standard profiles & related permission

    Often you want to deploy Admin profile and (x) custom profiles. Compare and deploy picks up hundreds of entries for standard profiles which are surplus to requirements. A single click way would be veryuseful.

    4 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. Specified Test Level Suggestion

    Hello,

    It would be very nice to be able to have a test classes suggestion when doing a deployment with "specified test level". The suggestion will ensure the package elements will be covered at least by 75% and so speed up the 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)
  5. allow multiple slack webhooks per scheduled monitor or test run.

    I have multiple slack teams, I'd like the ability to hook up a monitor org, or a test run to send to multiple slack webhook urls.

    Not super important, and I suppose I could get around it by scheduling a duplicate, but that just felt wasteful of everyone's API's. :)

    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)
  6. When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments

    When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments

    The SharedTo User doesn't exist in the target org causing my deployment to fail.

    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. 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)
  8. Differentiate XML and Code differences in the comparison

    I would find it very useful if the comparison result highlighted if the difference was in the XML or the Code (or both) for each item. This would especially save time when there are a lot of differences.

    7 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. Specify tests to run on the test monitoring jobs

    Some of my orgs have many tests, and I don't always want to run all of them on a daily basis. Being able to specify which tests are run daily would be great.

    7 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

    2 comments  ·  Testing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Exportable metadata reports for orgs

    Being able to export a summary of an org's metadata state for reference, prior to a deployment or as part of our reporting, would be great.

    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. Provide option to disable parallel apex testing in Scheduled Tests

    Scheduled Test runs can fail due to UNABLETOLOCK_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…

    9 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

    Under review  ·  1 comment  ·  Testing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    10 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

    2 comments  ·  Bug  ·  Admin →
    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 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.

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

    8 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)

    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.

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

    69 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)
  16. 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.

    80 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)
1 2 55 56 57 59 Next →
  • Don't see your idea?

Feedback and Knowledge Base