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

239 results found

  1. Ability to delete app visibility

    As per the official reply from Gearset support

    ".....The issue is, if you manually delete the app, all the app visibilities will be deleted as well. But when using Gearset to delete the app visibilities, they are not completely deleted but set to false. The best workaround for this is to manually delete the xml from your git branch. ..."

    If Gearset can incorporate this feature, it would be nice.

    The workaround is not that hard as it may sound. 4 apps in 60 profiles takes about 10 mins to mass-find and mass-replace in VS Code.

    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. Include "Messages reported by Salesforce" during Metadata Deployment in the final report

    During a metadata deployment, on the "deployment in progress" screen, there is a column for "message reported by salesforce".

    I think these should be included in the final results screen, and perhaps in the deployment report.

    These can be useful for the user to do things like make changes to their flows to conform to salesforce best practices.

    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. Provide deployment options for Mulesoft via Gearset

    As Gearset does Salesforce based deployments so well, it would be great to have Mule deployments done through Gearset 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  ·  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. Add configurable email reminders for scratch org expiration.

    From Salesforce orgs and Dev Hubs, it would be great if there were a setting that would automatically send an email when a scratch org is approaching expiration. This could be configurable per Dev Hub, and would help prevent data loss at scratch org expiration.

    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)
  5. link deployment to a salesforce case

    The ability to link a Gearset deployment to a salesforce case record. If an org uses cases to track a bug or feature, this feature would close the loop from that case to the gearset deployment.

    I understand that there is a post to chatter functionality but it would be nice to target a specific case for auditing purposes.

    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. Yellow help icon

    i love the help you guys provide, really great.
    Suggestion.. The yellow circle that you open and drop down.
    1) can you move it to the header, and if there is a pending message show the yellow circle with a number in it ( number is count of pending messages )
    2) can you make it a separate window model? typically when i am chatting, i need to see the entire screen and the current pinned model is usually in the way and i need to click the arrow to get rid of it.
    If i could drag the window…

    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)
  7. Ability to turn rules/processes off as needed with ability to rollback

    There are times when need to update data or load data into Salesforce org and need to turn off rules or processes before updating data or loading the data. When doing a data deployment, GearSet has this ability, and I would like to have this ability to do this without a data deployment. Ability to turn off Validation Rules, Required Fields, Restricted Picklist, Workflow Rules, Flows/Process Builders, and Triggers one by one or turn off all. Then roll back once finished updates.

    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)
  8. Release Branches

    If I create a Release Branch from UAT, I no longer need all the individual Feature branches.

    Inspired by Gitflow and the current Gearset Expanded Branching Model.

    Currently: The Expanded Branching Model will create a Feature Branch PR to main for every Feature branch that is merged to UAT branch.

    Desired: When I create a Release branch from the UAT branch, then Gearset should close all the current Feature Branch PRs to Main Branch - if and only if the Feature branch was already merged to the UAT branch.

    Related to: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/46150366-branch-pattern-matching

    This is related to branch pattern matching because…

    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)
  9. Link to the Salesforce Validation in Progress from the Pipeline

    When I deploy using the standard deploy interface, there is a link that allows me to view the deploy progress in Salesforce.

    In pipelines, I would like this same feature. When a deploy has been running for a while, it's useful to know where it is in the process and a quick link would be quite nice.

    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  ·  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. Incorporate Relationship Graph into metadata deployment

    Right now is it not possible to deploy Relationship Graph metadata according to https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_relationshipgraphdefinition.htm with Gearset. This metadata is required for the so called Actionable Relationship Center, which is part of Financial Services Cloud. Even though the meta data is available in the Vlocity filter in Gearset, the items we are looking for doesn't fall under that one. If selected, no meta data get retrieved and therefore no deployment happens.

    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  ·  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. Provide and enforce branch naming conventions

    Branches get all kinds of really stupid names over time. It would be nice if Gearset provided an option to template new branch names. For example when my users need to create a new feature branch for their user story, Gearset should prefix that branch with 'feature/'. When a release branch is created it should be prefixed as 'release/'. Bugfixes or Hotfixes could be bugfix/ or hotfix/.

    Dictating naming conventions is unenforcable. Keeping branch names organized goes a long way to keeping the repository maintainable over long periods of time. Even if folks are well intentioned, git branches are case…

    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)
  12. Enable a consistent, buildable set of Metadata for Releases

    I'd like to have a way to work with a consistent set of metadata items for a release, that I can add, remove etc, and consistently deploy into a variety of sandboxes and ultimately Production.

    Currently, if you clone a previous deploy, items are de-selected if they're the same between the environments being compared. That means once I've deployed, I can’t ever get that “list” of items back and I have to rebuild it every time.

    A likely scenario is that I've deployed some metadata from Sandbox A -> B. Lets say it's 5 Apex classes. I then realize that…

    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)
  13. language

    Gearset UI Language specification. Allow users to specify which language they want the UI presented in and then show the correctly translated terms in that language. When using google to translate the UI the words it chooses are not always relevant.

    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)
  14. Allow Filters to be Customised in Pipelines UI

    Currently, you can create new filters in Compare & Deploy, but when you are comparing and deploying from within the Pipelines UI on your development org, you can only select existing ones. This either means you have to get your team to go into standard Compare & Deploy to set up specific filters first, or they always have to select the filter that includes everything.

    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)
  15. Change language to focus less on Source Controls and be more user friendly

    Gearset is great for non-technical users or those that find Source Control daunting. However, the terminology used in Source Control has leaked over to Gearset, and I think this detracts from the useful aspects of it, and at times just makes it feel like an extension of Source Control.
    e.g. "Create Pull Request" in the Pipeline UI should be labelled something more friendly like "Request Feature 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

    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. Hide the "Create Pull Request" button on Deployment Success Screen

    Currently, we are setting our team up to use Pipelines, which has the benefit of guiding users down the pipeline in the right way (they can't create a pull request from a qa branch straight to main without going to uat for example). However, when they perform a commit from an org to a feature branch, the Deployment Success (commit success) screen has a button that allows them to create a Pull Request directly to any branch that they want. There should be an option to hide this from users, especially given the benefit of only being able to move…

    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)
  17. Enable admin visibility into a Gearset team member's shared orgs

    As a Salesforce implementation partner (SI) I have a lot of organizations to manage, well over 50. Each time a new org is added, I can go through and add all the users to that org, but whenever a new person is added to my team, I have to go through each connection and add that user to the list.

    As the owner, I would also like to be able to see all the shared orgs inside my account, so I can centrally manage them, rather than just the ones that team members may have added.

    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)
  18. Send Email when a package is Validated successfully with PDF of Deployment Summary.

    We currently receive an email with deployment summary as PDF attachment after successful deployment, but we also want this feature for successful manual validation. This is help us review the validated package summary with Deployment approval teams in our ORG.

    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  ·  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. Allow account admins to run reports on their team's usage of Gearset.

    I am managing a Gearset account and I need to be able to know who is using Gearset and who isn't so I can more properly assign licenses.

    This might be an Enterprise feature, https://app.gearset.com/account/account-report, but really should just be something an account admin can run.

    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. Only notify the Pull-request creator on validation errors

    Hi team, not sure if there is a way to do that in the current setup, but I think it would be helpful to add the option to only notify the Pull-request creator/owner on the validation errors, instead of "hardcoding" the email recipients. Regards, Adrian

    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  ·  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