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

1289 results found

  1. See when a commit validation was deployed or not (For CI validation Jobs)

    When you go to the validation only CI jobs section within the Continues Integration part we usually have a CI job targeting a prod environment, you can see all validations succeeded and the commit attached to such validation, each CI job run contains 3 options:
    View comparison
    View Summary
    Deploy

    Then if the validation passed and the code indeed was merged from the feature branch to the master branch (Which would have triggered the actual CI job run), how would you be able to identify wether a merged pull request was deployed or not within gearset?

    For me it's very…

    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)
  2. View on GitHub for custom git repository

    Offer the option to "View on GitHub" for custom git repositories in Commit successful screen

    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

    1 comment  ·  New feature  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Create JIRA ticket when CI Job runs sucessfully

    I undrestand that gearset can update status, comment and attach report to an existing JIRA ticket once a deployment is successful, but it would be nice to have a feature that would automatically create a JIRA ticket once the CI Job runs, and deployment is successful, for reporting and internal auditing

    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)
  4. Ability to Template Scratch Org Settings

    It would be great if it was possible to template the scratch org creation screen.

    We have a lot of managed packages that need to be installed and having to enter the ID and Key every time is very time consuming.

    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. Data deployments should ask if you want to Insert or Update or Insert & Update data

    Data deployments should ask if you want to Insert or Update or Insert & Update data.

    Currently it always performs data upsert only

    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

    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. It would great to be able to monitor certain user actions, such as exporting a report in Salesforce.

    Right now, I am only aware of having to purchase an add-on from Salesforce to be able to get this information.

    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)
  7. Additional text countries

    I'd like to see a few extra countries added to the text messaging option on scheduled deployments. My team works with resources in different regions.

    Brazil +55
    India +91
    Philippines +63

    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)
  8. Add the ability to report on validations and deployments via CI

    Currently, it's not possible to see a report on when a validation or deployment started and ended for a given CI Job across multiple PR's. This will help understand how long on average validations or deployments are taking for a given environment.

    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)
  9. Add to draft deployment as you build

    Ideally I'd be able to add metadata to a draft from within salesforce - via a chrome addon maybe?

    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

    0 comments  ·  New feature  ·  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. enable linking two separate gearset accounts when they are hooked to the org

    I've been using Gearset for a few years. The Salesforce consultant I occasionally work with just started using Gearset with all their clients. So we both have a connection to my Salesforce org. It would be nice to see a combined view of deployments, validations, test runs, etc. made against my org - regardless of which Gearset account it was done from.

    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. enable linking two separate gearset accounts when they are hooked to the org

    I've been using Gearset for a few years. The Salesforce consultant I occasionally work with just started using Gearset with all their clients. So we both have a connection to my Salesforce org. It would be nice to see a combined view of deployments, validations, test runs, etc. made against my org - regardless of which Gearset account it was done from.

    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)
  12. Field Dependencies for Reports

    When deprecating a field and replacing it with a new one, we need to be able to see where they are used in all reports, including private folders, which the "Where is this used?" feature does not detail.

    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)
  13. Force a full production backup, and forbid its deletion

    I was not able to buy this tool because to me it was a blocker that we have the right to delete the production backup.
    I may agree that the we don't force for a full backup, but leaving the option to descope tables is equivalent as not backing up.
    Force at least an initial configuration and allow only to add more scope to the backup, but never to reduce it or delete without contacting your support who should get an authorization from more than one person on the client side.

    If I'm an admin at salesforce, and an admin…

    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

    1 comment  ·  Data backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. One-click Sandbox data deployment of all objects

    I think a great feature would be for the tool to be able to copy all object data from one org to a sandbox, and if the amount of data is too large for the sandbox, allow the user to specify what objects to take sample data from - and how - i.e. take no data from a certain object,or take 5% of the latest created data, etc. It would be helpful to show the objects that have the most data.

    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

    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Easier way to exclude multiple named items in the metadata filter.

    In the metadata filter named items, I want to exclude 10 named items. Currently I have to use the "exclude" Object name button 10 times. I want to tick all the 10 named items, that currently allow to include, and click a button to turn them into "exclude" in the named items.

    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

    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. When creating a Pull Request from Gearset have the option to default to another branche

    After you did a deployment from a sandbox to GIT (Github in my case) you have the option to create a Pull Request right from that screen. The default target branche is "main" even though my default branche in Github is set to develop.
    It would be great if Gearset follows that default branche that is set in Git OR has a way of defining default target branche in Gearset.
    The risk now is that someone might overlook this, make a pull request against main, someone else also overlooks this and merges it into main. With CI jobs on main…

    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)
  17. Provide help link/button on each analyzer problem pane with specifiec discussion

    Suggestion
    In "Problem Analysis" page, the problems indicated and solutions are not necessarily obvious and understandable.

    The suggestion to read more about the analysers in the user guide is in the case I'm facing an enormous challenge.

    Copy and paste the problem into your search mechanism brings back endless answers - not one used the wording in the problem statement!.

    Here's an idea, have a button/link with each problem that take one to the user guide section (or other documentation) exploring the problem.

    No hunting for answers as the 1st choice to figure out what your product is saying. It'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)
  18. Additional feature - GITHUB Pull Request validation in CI Job

    Checkbox - Pull requests: Validate pull requests targeting the source branch is only visible when Run Job is set to --> Run tests based on Apex changes in the package

    Request you to enable option even when this is set to Run Job: 1 / 2 /4 / 24 Hours

    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)
  19. Add csv file results as attach

    attach a file to Teams after code analitics with incoming Webhook

    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

    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Add Comparison Column for "Environment"

    Add a column for "Environment" which signifies which environment the change took place. For instance, this would tell you whether the changes took place in Production Only, Sandbox Only, or both.

    Then, I could filter by Sandbox Only and both to see only the changes I made recently in the sandbox that I need to push to Production. Right now, I have to sift through the many little changes to items that occurred in Production.

    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)
  • Don't see your idea?

Feedback and Knowledge Base