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

1314 results found

  1. I would like the ability to auto promote updates to inflight feature branches

    When using feature branch promotion in pipelines, I often find myself in a scenario where I’ve pulled a new feature through the pipeline to one of my static environments. I then test it, discover something that needs to be changed, make the change in the dev environment, and pull that change through the pipeline again so it reaches the same static environment for retesting.

    I would like functionality that enables me to release a new change to that branch from dev and have it automatically promote through all static environments, stopping at the current one where the original pull request…

    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)
  2. add preview of archived files and let admin choose fields to show on the related list in Archive Viewer

    Please improve Archive Viewer with a preview of the files Archived, like the current document viewer on SF and consider to add more functionalities on the related list shown on Archive Viewer, like choosing fields to show and search bar incorporated.
    These functionalities are already available with other Archive apps connected to SF.
    Let users select the record to restore directly from the related list in Salesforce.

    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)
  3. Using Back Promotion for single Environments only and selective PR's only

    We normally update our developer orgs with the "update sync" function after the PROD release. However, sometimes we have changes that are build on top of each other but developed by multiple devs and therefore orgs.

    In that cases, it would be nice to turn on "back promotion" but only for certain environments where it is needed and not globaly. In addition, being able to selectively create back promotions for PRs would be nice as well.

    At the moment, if the feature is activated, Gearset is creating a back promotion for every PR, regardless if it is needed or not.…

    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)
  4. Changing API Version should make it obvious to save filter before CI Job can be saved

    It's a usability bug, I think.
    When you change the API version in a CI Job, the button to save CI Job greys out but has a spinning dial of 'Something happening'. Actually the system is doing nothing, it is waiting for the filter to be saved (even if the filter wasn't saved before) but this is completely unclear.
    Changes then
    1. auto-save filter or bring up the 'save filter' modal
    2. Show a toast message saying "save filter"
    3. Button should grey out with hover text of "save filter", no spinner

    I waited longer than I care to admit,…

    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  ·  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)
  5. Select All PRs for promotion

    When promoting PRs from one environment to another in the pipeline, it would be useful to have a "Select All" option

    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)
  6. Update Test naming convention matching to work with implementation classes

    We are using fflib and the AEP enterprise design pattern. As part of this design pattern we have interfaces and implementations for our Service layer classes. E.g. we will have something like ILumpSumService and LumpSumServiceImpl. When we create a test class it would be something like LumpSumServiceTest. So it would be great if the logic could be updated to match use cases where you have an implementation class like that. Also, I think any net new test classes added should be executed no matter what

    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  ·  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)
  7. Have the ability to see the metadata comparison between a merge-branch and the destination environment in Pipelines

    Greetings,

    I would like to request the ability to see the metadata comparison between a merge-branch and the destination environment.

    For example, my pipeline is setup:

    Developer's sandbox --> QA sandbox --> UAT sandbox --> Production

    with the repository branches (merge-branch) for each sandbox respectively:
    merge-QA
    merge-UAT
    main

    After a feature-branch passes its validation and is merged into the merge-QA, I would like to be able to see the metadata comparison of what is about to get deployed to the 'QA sandbox'. We have the ability to see the contents of the commit via the link to our repository hosting…

    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. Allow multiple team members to be assigned to a single sandbox on the pipeline view

    Currently a single team shared sandbox can have multiple users with delegated access. However, only one of the users can view the sandbox in a pipeline view. In order to allow multiple people to see the sandbox -

    Current solutions:
    - Add the same sandbox multiple times and assign each to the required team members
    - Or, allow all team members to see all sandboxes

    Suggested solution:
    - Allow multiple team members to be selected via the "Assign sandbox to team member" function.

    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)
  9. Flow Navigator, show more information in Settings (Trigger Order, Status)

    within the Settings Section, please show more data

    Absolutely missing: Trigger Order (It is compared in the XML)
    Label (Currently Interview Label is shown, but that can be different from Label, we need both)
    ProcessType

    Others?

    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)
  10. Ability to Select and Merge Specific Changes in Lightning Components and Flows

    We are using Gearset to compare and merge changes in Lightning and Aura components, as well as Salesforce Flows. While the tool works well overall, we’ve noticed that it currently lacks the ability to select and move specific changes during a merge. Instead, it requires replacing the entire file, which isn’t ideal in many cases.

    It would be extremely helpful if Gearset could allow selective merging of specific lines or sections—similar to how it works for Apex classes. This feature would greatly improve control and efficiency when working with Flows and Lightning components.

    Thanks for considering this enhancement!

    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  ·  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. Put a "Simplify Differences" toggle at the entire comparison level instead of each item

    Add the "Simplify differences" toggle to be enabled at the entire comparison level so you can filter out items that don't have any actual changes besides metadata being moved around within the xml file by the salesforce API. This way, if there are items that don't have any true differences, they can be quickly filtered out at the comparison level instead of drilling into each one and having to "simplify differences".

    This would help especially with custom objects, where the salesforce api moves the Action Overrides around causing the analyzer to flag objects as different between orgs, when in reality…

    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. Add an integration for Google Chat that includes an integration for Change Monitoring and Unit Testing.

    Recently, it seems that Google Chat has reached some feature parity with Slack in that it has a defined integration avenue for adding notifications to Google Chat. I have found that I can set up a custom webhook to Google Chat for the CI jobs, but webhooks are not available on the other 2 features I am looking for notifications from.

    I would either like to have:
    a.) An integration for Google Chat with an app on the Google Chat side that we would add for the connection to our Gearset
    b.) Webhook availability for more notifications, so I can…

    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)
  13. Auto merge of PRs

    Once the validation process is successfully completed for the respective PR, it would be very helpful to have an option for automatic merge and deployment. This would streamline the release process and reduce manual steps.

    Additionally, it would be great if we could have control at the org level to enable or disable auto merge functionality. This way, teams can decide whether they want to use auto merge based on their workflow preferences or organizational policies.

    Thank you for considering these enhancements!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Improve UI of Analyser, 'Some items reference components that aren't in the target'

    This analyser, does provide suggestions on metadata items to be included, but it does not mention the why.

    Today I got the suggestion to include something, which I had no intent to include, but I could not find WHY, Gearset would like me to add this to the deploy.

    Providing the reason, makes it easier to adjust the deployment, maybe remove an item, or uncheck something I accidently added to 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)
  15. Pick up test classes to run from the apex class

    Add a variable in apex classes where we can specify which test classes to run.

    Recently you added the ability to specify the test classes to run on a pull request, which is great!

    I know <ApexClassName>Test are automatically picked up by GS, but would be great if we could specify with
    @TestClasses('CaseTestSuite,LeadTestSuite') or similar in the actual Apex Class and Gearset would automatically pick it up and add those test classes to the pull requests .

    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)
  16. Customizable Metadata Deployment Order - Destructive change and reference changes

    We should be able to define the order of metadata deployments. For example, when deleting a custom field and updating its references, we currently need two separate deployments: one for modifying references and another for field deletion. Allowing us to set the deployment order—modified references first, then field deletion—would enable this in a single deployment, streamlining the 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Delay Jira status updates until after post-deployment steps are completed

    Currently, when using the Jira integration with Gearset pipelines, status updates happen immediately after the initial deployment completes, but before any post-deployment steps are executed.

    We need the ability to configure Jira status updates to occur only after ALL post-deployment steps are successfully completed. This would ensure tickets only show as ready for validation when they're truly ready to be tested.

    This is important for teams that have mandatory post-deployment steps (like data imports, configuration changes, or additional verifications) that must be completed before a story is actually ready for testing. The current behavior can lead to confusion when testers…

    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)
  18. Allow environment variables be applied to all environments except specified

    Allow environment variables to be applied to all environments and specify exceptions for which they should not be applied.

    For example, if an email address is stored in source control as prodsupport@example.com it should be transformed to sandboxsupport@example.com for all environments except prodcution.

    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)
  19. 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)
  20. After a package is validated, link to the Salesforce Deployment ID

    Gearset already does this for a deployed package, that on the Deployment Summary page it shows the Salesforce ID of that deployment. Can we provide the Salesforce ID for a validation build against a Salesforce environment as well?

    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)
← Previous 1 3 4 5 65 66
  • Don't see your idea?

Feedback and Knowledge Base