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

1357 results found

  1. Limit Connections creation

    Currently there is no feature to prevent users in creating their own connections within Gearset.

    We need users to follow the permission that was setup on the shared connection. We have only 2 users that have the approval to deploy code from a sandbox to production. As they can set up their own connections then this bypasses our restriction

    Having a permission only available to the Enterprise user or a user approved to create connections and delegate access would prevent the bypass of access permissions

    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

    2 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)
  2. Set values on record creation for fields that can't be updated

    Some objects, for example PriceBook Entry, must have their attributes set on insert as once created most of the record is not updatable, e.g. CurrencyISOCode cannot be changed on this record once it has been inserted. Providing a way to set these fields on creation, rather than a later update step, would allow these records to be deployed as currently PriceBook Entry records fail in multi-currency orgs as they are all created with the default currency causing SF to treat them as duplicates

    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)
  3. Custom ordering option for CI Dashboard

    Rather than splitting jobs into Validate and Deploy and ordering alphabetically, allow custom ordering (drag and drop, or custom grouping) in order to maintain logical job sequences including a mix of deploy and validate jobs.

    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

    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)
  4. Control When Tests are Ran Based on Metadata type

    It would be nice to control when we want tests to run based on the type of changes in the triggering event for CI. Something like only run test classes on update of Apex Classes, Flows, Workflows, and Objects.
    This is a bit of a patch for not having test classes fully optimized but would be helpful with orgs who have lots of profile and layout changes.

    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)
  5. Allow custom manipulations to data during a data deployment

    Export the selected data source in a CSV file before deploying, in order to allow custom manipulation. Then allow the import of that CSV to destination - functioning like a more sophisticated Data loader.

    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)
  6. Show associated JIRA ticket in Validated Packages & Deployment History and Export

    We would like to view the associated JIRA in both the Validated Packages and Deployed History pages. In addition, we would like to export the associated JIRA tickets in the Export History Excel report, found in the Deployment History page.

    We link our Jira stories to our Production deployments and we would need a way to report on which ticket is linked to which deployment. Currently this is only available if users are diligent enough to also write the story number in the Friendly Name or Notes.

    This would be an extremely useful feature especially for companies undergoing SOX Compliance…

    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)
  7. Select source control based on actual setup/connections when starting comparison

    When starting a comparison and selecting source/target environments for Source Control - it shows all connection types including those that I haven't connected.

    With browser cache, it seems to remember the one you selected last. However, for new users (or when you clear cache) it'd be ideal if Gearset would default your source control on this screen to whatever the user has connected. Once a user has connected a source, there's no sense in having the user choose it again at this step.

    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. Add Additional Deployment Preferences for JIRA integration

    Currently the Jira Ticket Deployment Preferences don't give you enough options to manage the expected behavior with our process. Right now there is too much noise on our tickets and we want the option to reduce that. For example, we do not need to comment on the ticket when attempting to validate deployment, just as we don't need it for failed deployments (which you already have as a feature). We simply want a comment with the deployment notes when a deployment is made since this would reflect the actual system changes that took place with this feature/issue.

    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

    2 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)
  9. Show test apex run in the deployment report

    When we validate a deployment then schedule it for deployment. Once deployed we receive a report however the tests run do not show here and you have to back to the validated section to find them - please include the tests run on the final deployment report

    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

    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. Be able to log into scratch org from Deployment Success page

    It would be super convenient to log into the scratch org directly from the Deployment success page

    • From Compare & Deploy sequence
    • From CI success
    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

    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)
  11. Allow outgoing webhook option to be configured for Compare and Deploy

    I need the option to configure an outgoing webhook when deploying via 'Compare and Deploy' feature. Currently webhooks are only available with the CI jobs.

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

    1 comment  ·  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 customize CI Dashboard

    We have a number of different teams using Gearset with a number of different CI jobs. I don't care to see their jobs in my dashboard and they don't care to see my jobs on their dashboard. It would be great to be able to customize my dashboard so that I only see the jobs I'm interested in. Maybe it's some sort of flag on job to be able to add/remove from dashboard or maybe its a separate tab called 'My CI Jobs Dashboard' that we could default to when opening CI Jobs. Thanks for your consideration.

    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

    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)
  14. Add an option to not run the comparision part in CI job (sfdx like)

    When you are pushing a project with sfdx, there is no compare, sfdx just push the whole package.

    It will save a lot of times.

    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)
  15. 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)
  16. Metadata filter - ability to select Report/Dashboard folders by parent folder name

    When setting up a metadata filter for a new comparison, when it comes to Reports and Dashboards, it would save sooooo much time if they could be selected according to the top-level/parent folder that they reside in. That would enable the ability select all reports within a single parent folder at once, rather than having to select reports separately which reside in a nested/child folder.

    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

    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)
  17. Link to salesforce source records

    When reviewing a Comparison with Salesforce as a source or target, include a link to the Setup/Configuration page that is being compared. For example, a link to a Page Layout that the user could click to jump right to the Layout in the appropriate Salesforce environment. There are times when we review Comparisions and need to see the source outside of Gearset and this gets the user there much faster.

    The link would appear in the header of the Comparison window, near where "SOURCE" and "TARGET" are listed.

    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

    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)
  18. Monthly sandbox refresh from production

    I would like the ability to refresh a sandbox from production on a scheduled recurring basis on a monthly cycle (ex: from prod to a full sandbox) so as not to overwrite current development items that are in process or testing.

    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

    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)
  19. Ability to change Formula Fields to other Field Types

    Gearset doesn't help with one of the most common deployment headaches: changing a formula field to a non-formula field type. It's still a nightmare even with Gearset.

    What would be awesome would be if you had a "Change Field Type Wizard" where we could say FormulaField1 needs to become TextField1 and it would do multiple deployments to accomplish the changeover:
    - get components
    - deploy temp field of new type AND update all existing components to reference the temp field instead of the formula field
    - deploy delete of formula field
    - deploy text field in place of the old…

    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

    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. call webhook with scheduled deployment

    We would like Gearset to call a webhook when a scheduled deployment completes. The message to the webhook should pass a message with the org name, UTC datetime, the deployment friendly name, URL of Gearset deployment results and a status field with 'succeeded' or 'failed'

    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

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

Feedback and Knowledge Base