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

1122 results found

  1. Quick deploy in pipelines

    It would nice to be able to use the Quick Deploy feature once a release is validated, instead of either hitting deploy or scheduling the deploy and having it validate one again.

    14 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. Remove files from a PR

    I want the ability in Gearset to selectively remove files from a branch or PR without running another comparison.

    I have an admin that frequently "over commits" too many things.

    Often its bad enough that its just easiest for them to delete the branch in github then start over in gearset.

    The problem then is that starting over from scratch, a day or two since they worked on it, and they will make a different mistake.

    I'm aware of a few features, like

    1. Delete the branch in Github and start over in gearset

      • Seems to be the easiest to me
    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

    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. Implement a Ticketing Feature

    Salesforce DevOps Center has a useful feature that allows users to create different Projects that have their own pipelines. Within each Project, you can create Work Items (similar to Issues in Jira). The user can then perform their work in a Salesforce environment and then run a comparison to associate certain changes to respective Work Items.

    From there, each Work Item can be promoted through the various environments in the Project pipeline.

    This is really helpful when working on numerous tickets/features for a given project, knowing exactly which environment each Work Item is in and the various metadata elements that…

    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)
  4. Configure the "Saved Comparison Pair" to always use a specific Comparison Filter

    When managing multiple orgs, and running comparisons, the Saved Comparison Pair saves a lot of time. However, sometimes we need to use different Comparison Filters, based on which environments we are comparing.

    Instead of first choosing the Comparison Pair, then manually selecting the Comparison Filter to use, it would be great to be able to (optionally) configure the Comparison Pair to use a specified Comparison Filter.

    Example Use Case:

    When committing work from our Dev org to BitBucket, we exclude Apex Classes & Triggers, and mainly commit declarative functionality (Apex code is committed separately from our dev team). All development…

    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)
  5. Add pipeline support for CPQ

    CPQ deploys to and from Github/Salesforce so it should be a relatively simple issue to include this in the pipeline deployments. You could add a checkbox or just warning to ensure that triggers are manually disabled when that is needed.

    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)
  6. Ability to remove PR's from a created release

    WHen working with pipelines, when we create a release and we merge PR's to the release so we can then deploy later, it would be nice if we have the option to remove them in case someone change their mind instead of cancell release and srtart over

    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)
  7. Automate Jira Status when a Pull Request is created in Pipelines

    Presently, the capability to automatically update the Jira Status of a ticket is limited to transitions occurring between different environments in Pipelines. Enhancing this functionality to include automated updates triggered by the creation of a Pull Request would prove beneficial, eliminating the need for manual intervention when transitioning to stages such as "Code Review."

    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 "View Validation in Salesforce" to your Github and Teams/Slack Channel messages.

    Our pipeline is utilized by some implementation partners that we do not give access to Gearset. They manage their changes that flow through the pipeline with GitHub and receive pipeline updates in a Teams channel. Both of these options have a message to view validation errors in Gearset but the partner teams cannot see Gearset. If these messages included the same "View Validation in Salesforce" option that lives in Gearset, they could be redirected to the Salesforce error page to help their troubleshooting faster.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Get Notified if Pull Requests or Validation Fails

    Our Org has Gearset Officers who handle promotions. It happens at times that I create a pull request and have it start validating (which can take a while). I'll navigate away from the screen and totally forget about it, assuming it'll get pushed to the next environment.

    But sometimes there are merge conflicts, or validation fails. I'd love to get a notification, either in email, or as an integration to an attached jira ticket that it failed. That way ill be notified by slack or whatever.

    Just an addendum here. We use 3 environments. Admin, UAT, and finally Production. When…

    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

    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. Delta comparison between two unit test reports

    Hi team. Would be good to have a feature that allows us the comparison between two unit test results. We are interested to export the delta errors from one day to another.

    Use case: We are executing deployments for more than 50 pull requests against the same target sandbox, hence regression errors might be introduced throughout the day. We are running nightly unit test jobs and usually, in the morning, we have extra tests which are failing comparing with the previous day.

    We are currently exporting the gearset errors from 2 reports, in Excel tables, and compare these ones to…

    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)
  11. Improve audit API to extract list of users and their entitlements. Additionally, allowing us to provision & deprovision user access via API

    We use 3rd party tools to audit all of our user access at our company. Automating this via API instead of exporting CSV and loading that into another tool would be very beneficial. Additionally, we use that tool for provisioning and deprovisioning so if an API for that existed too, we could automate Gearset users.

    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. Ability to automate deployment to a particular environment without manually promoting changes

    When there are multiple Salesforce environments in the deployment pipeline, like Integration, Qa, Stage and Production, we would like to have ability to automate deployments to a specific environment, without having to select PR and promote changes manually. Most of the times SIT/Integration environment will be used for Developers to be able to perform integration testing, where we do not want someone like a Lead to review and promote PR manually. It will be beneficial to deploy the changes automatically, as soon as someone creates the PR to the Integration environment.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Delete feature branches in Github in a way that they can be restored

    I closed a PR to master, and Gearset deleted the feature branch. However, it wasn't merged, so I wanted to restore it to continue work. I was completely gone from Github. I believe Gearset should do a normal delete that allows restoration instead of completely obliterating feature branches or allow an option to do so.

    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)
  14. default repository

    Allow to set a default repository when you have multiple repositories.

    1. Navigate to Compate and Deploy
    2. Select Source Control and select a VCS(in our case Gitlab Self Managed)
    3. If you have dozens of repositories they all show up on the list
    4. Need ability to specific a default repo which will be auto selected
    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)
  15. Show Created by and Created Date in Comparison view

    I'd like to see created by and created date in the comparison view. Sometimes we have multiple users working on items and I may not be the last to modify something but I am the one to deploy it and if I am the creator, I know what it is named but it makes it hard to sift down if I can only show modified by and modified date.

    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)
  16. Bulk resolving merge conflicts across multiple PRs (set resolution as Feature or Environment)

    It would be great if there was the capability to bulk-apply Feature or Environment when resolving merge conflicts across multiple PRs. I have a few dozens that all need to be set to the same option, and it would be useful to handle this quickly rather than click on each one individually.

    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)
  17. Expand integration for our Pipelines to allow us to enable tools like SonarQube and Veracode to run as part of our DevOps process.

    We use tools like SonarQube and Veracode within our company to improve our security and code quality. It would be extremely helpful to have integrations with these tools or an open integration we could configure to work with them. Especially if that could be triggered as part of our pipeline process so this interaction is automated.

    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. Add omni components to filters through metadata API

    Now that Salesforce has moved omnistudio into standard runtime (as opposed to managed package) and also added the omnistudio components to the metadata API, the following components:
    omniDataTransform
    omniIntegrationProcedure
    omniScript
    omniUiCard

    Since these components are in xml format, it is much easier to see differences in source control.
    It also removes the need to perform separate deployments for the Salesforce metadata API and the vlocity build tool.

    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. Improve Github Authentication and Access Control

    While authenticating with Github, GearSet asks for too many access request including read/write access to all public & private repos which doesn't make sense.

    Alternate Custom Git Auth does not allow teams to create team wide CI jobs.
    And with User - specific CI Jobs, It does not allow us to setup "Validate open PR" jobs.

    Please provide better resolutions on authentication and job setup processes.

    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. Environment variables - Clone

    Hello Team,

    We would like to have the possibility to clone already existing Environment Variables when setting up a new Environment.

    This functionality will allow us to refresh and create new environments faster and prevent us from performing specific commits in branches and specific configs per new environment.

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

Feedback and Knowledge Base