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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Metadata Filter organization with group or tag management

    It's great that we can set filter visibility now to Only Me or to share with Team. It would be nice, especially for larger teams, to have another way to organize them either with tags, folders, sub teams or groups.

    Example: 1 Scrum Team may have 10-15 filters they maintain and use, and another group of users on a team also have 5 or so they use. Both can see all 20, and this adds up fast.

    Feels like being able to group users together could also have other benefits like mass assigning access to orgs (for deployment, validation, comparison)…

    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

    2 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add a Select All that works on filtered items when setting up filters

    When setting up the filters, I would like the ability to do a Select All on just the filtered items so that I don't have to manually select each one of them. This would be a huge time saver.

    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

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  3. To add capability to mark (to ignore) not selected items to be able to remember that the particular item is not required to be deployed

    When compare source and target, sometimes u do an educated decision to NOT select something, and then selecting the rest of the items. Then if the compare results saved as a Draft Deployment, u may return back to it, and do a refresh for the comparison. In this case Gearset would kindly save all of the selected items. But for items that were not selected by the user, not they are mixed up with the new differences. So user have to remember, that this particular item he did not select intentinally, but this item that is not selected is a…

    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

  4. Add ability to clone deployment CI job to validation-only CI job

    This would save us time duplicating regex statements for the new job

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  5. Choose Delete action per Metadata Type for CI jobs

    In the past we had troubles deploying reports via CI, they were not showing/deploying, the workaround was to enable the filter to include all reports. This works to solve that, but now I am looking at including more into the repo and start using delete actions in the CI jobs as well. The downside is that because we have to have all reports in the filter, the CI job will delete reports created by users in non-private folders. A freedom we want to give certain users in Production.

    What would be an epic enhancement (and solve this challenge) is if…

    22 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

    5 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to select source target for Successful Deployment Notifications

    Currently successful deployment notifications send every success to the specified addresses. Having the ability to specify the source would eliminate the unnecessary notifications to those addresses. We have a use case in which we only wish to send notifications for successful deployments to our production source.

    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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow Package Version Mismatch Bypass for Org Deployments

    When deploying a branch to a Salesforce org where there is a managed package version mismatch in the file metadata, it would be nice to be able to bypass this discrepancy as there are occasions where there may be a newer package version in a lower/sandbox org and an older package version in a higher/production org.

    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

  8. Connection List Search Feature

    Add a Search feature to Connections Page. I have 59 connections at the moment and the only differentiation between them is a suffix at the end of the login. It would be nice to be able to quickly search the list of Connections like a CTRL + F would do.

    I often have to scroll the list and compare login usernames.

    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

  9. To give the option to export , Class wise test coverage report in some Excel format

    To give the option to export , Class wise test coverage report in some Excel format

    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  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  10. Refresh specific item in comparison through context menu

    It would be great to refresh a specific item within a comparison that I know has changed since the last comparison.

    68 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

  11. Allow orgs to be grouped in folders

    On the “My Connections” page, I'd love to see an option to add a folder (and sub-folders).

    Currently, there are options for "Developer orgs", "Sandbox orgs", "Production orgs", and "Scratch orgs".

    If you are running more than one entity, having the sandboxes related to a single entity inside of a folder would be more user-friendly than having multiple dev/sandbox orgs inside the same folder.

    For example, if I'm managing deployments for "ABC Company", "XYZ Company", and "LMNOP Company", and each has multiple sandboxes, it would be really convenient to be able to separate out their various sandboxes more effectively, into…

    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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  12. SFDX projects and source format and CLI useage

    Gearset CI only supports SFDX source that follows the SFDX project template structure (e.g. force-app/main/default/classes and so on). However, SFX CLI doesn't mandate that structure.
    SFDX allows you to group metadata by function or logical group (so you can combine metadata in any way that makes sense to you) . We have many projects like this that gearset cannot deploy.

    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

  13. Users should be able to specify test classes and save them to draft deployments

    Users should be able to specific and save test classes in the comparison stage so they can be saved in draft deployments. Seems like a waste of extra steps to unclick tests and select tests over and over as you work through a deploy.

    also when deploys are combined, they would get all the test classes, again, saving lots of time.

    6 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  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add additional controls to Monitor

    Hello Gearset,
    We are exploring using the "Monitoring" functionality to audit our Salesforce production metadata changes for our IT Controls. It looked promising until we found out that anyone on the team can edit any monitor job setting, which creates a loophole in the controls that we can't monitor the monitor.
    So I'm curious to learn from Gearset whether any of the following can be done/requested:
    * Can we limit the Monitor jobs to only be editable by the person who created it?
    * Can we show either an audit history or LastModifedBy/LastModifiedTime of the Monitor job?
    * If the…

    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  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  15. Run all tests only when have apex classes in the package

    Hello,
    I want suggest an option to avoid run unit tests when no have apex class in the package.
    And run all tests when have any apex class in the package.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  16. CI Job History - Show what CI runs were manual and who triggered the manual run

    It's nice that the CI job history shows the source commit link for the auto triggered deployments from Github merges, but for visibility and transparency it would also be good for users to see when a job was triggered from a manual run and what users ran it.

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  17. Archive or hide Automation jobs

    On each of the Automation dashboard views (Monitoring, Unit testing, Continuous integration) it would be nice to have a way to archive or hide job. Often times previously setup jobs that are not active but would be good to keep for historical reference can clutter the dashboard.

    5 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  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  18. Prevent Deployments from Including LiveChatButton with Omni-Channel Routing

    https://developer.salesforce.com/docs/atlas.en-us.apimeta.meta/apimeta/meta_livechatbutton.htm

    LiveChatButton metadata that is routed using OmniChannel is not supported with the Metadata API and the deployment will fail.

    It would be great if Gearset had an analyzer to remove this for end-users to prevent the error.

    The following property is null for LiveChatButtons routed through Omni-Channel

    <routingType xsi:nil="true" />

    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  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  19. Need to have JIRA integration with Data Deployments

    Need to have JIRA integration with Data Deployments which will improve the process and allign it with meta data deployments

    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  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add Salesforce ID to Export History button

    Can you add the Salesforce ID to the Export History button for reconciliation purpose.
    We currently have to manually match the Salesforce ID in Gearset with the Salesforce ID on the Salesforce Deployment Status page to get the reference between the source ticket in Jira and the deployed change for compliance purpose which is a time consuming process.

    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  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 34 35
  • Don't see your idea?

Feedback and Knowledge Base