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.

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Give users the ability to update field/object permissions for specific profiles only

    The issue is, when promoting from one org to another and changing either Custom Object Permissions or Custom Field Permissions and if more than the profile you want has been changed, the extra profile changes get promoted anyway. So we need a way to control which profiles get applied when promoting field and object level security.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  2. Need to move Help Menu between orgs

    I recently had to move custom Help Menu items between orgs. Since Gearset didn't support it, I was reduced to manually entering the data in each org since they weren't connected in Change Set paths. I believe the metadata is CustomHelpMenuSectio

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  3. Export snapshot of production org to git

    I'd like to be able to export a snapshot of all the metadata from my production org (include all components) to my git repository by clicking a single button.

    After every release, it's worth taking whole metadata export from the org to git for the next/on-going releases.

    For now, we have to create a couple of metadata projects to export the metadata to git, which is a tedious job and takes a lot of time.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  4. Deploy single layoutitems

    In Layouts there are multiple layoutItems. it would be helpful if we could to deploy single <layoutItems> from a Layout without affecting other <layoutItems>.

    4 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  5. Commit-by-commit deployment

    As you are giving an option to trigger the CI job based on repository commit, it would make more sense to only compare the source and target based on the commit items and consider the commit changes for deployment based on your selection of either new, modified or deleted and the comparison filter(which can be optional in this case).

    This will help in reducing the chances of overriding the changes of other teams working in a shared environment or an environment not in sync with the branch.

    There can be other scenarios where we maintain managed package items in the…

    17 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  6. Create Change set without comparison

    Allow user to directly create a change set without doing the comparison. If user has a list of items that needs to be migrated then allow the user to add items and skip comparison step.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  7. Provide an option to run Aura and/or LWC testing before deployment

    I don't think that very many people are actually creating Aura/LWC tests yet, but they really should be.

    Since SF doesn't require them like it does for Apex, if we decide that those tests ought to be run before deployment, it would be great to have Gearset run them. This will help us to make sure they are run before every deployment instead of relying on developers remembering to do it manually.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add Support for Pre/Post Data Deployment Scripts

    Some of my more complex data objects require that I turn off Validation Rules during deployment, then back on again after deployment.

    Options that would work:

    * BEST: List of Validation rules under each object and and option to temporarily disable on a one-by-one basis during the deployment. A "Disable All Validation Rules During Deployment" option would be helpful if this feature is implemented.

    * BETTER: Ability to specify metadata xml to apply to each sobject pre and post deployment.

    * GOOD: Ability to specify anonymous Apex to execute pre and post deployment. This would involve a callout to the…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data  ·  Flag idea as inappropriate…  ·  Admin →
  9. Show *all* matching items on All Items, even if they haven't been changed.

    I couldn't find a field that I was looking for today, despite searching for it specifically, because it was hidden inside it's parent object. I understand that the reason for this was something to do with there being no difference on the field (and I appreciate that the reason is to avoid clogging up the screen!), but if you're searching for a specific field, I think it should really show up...

    Took me bothering someone on live chat to figure out what was going on.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  10. Allow to add Custom fields to Source control without Account object in Source control. As we don't want to update existing Account object

    Allow to add Custom fields to Source control without objects in Source control. As we don't want to update existing objects in org.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  11. create a visualization of the DevOps process

    Creating a visualization of the DevOps process removes the need for separate Visio diagrams or visual aids to represent the process. Also by creating this feature, you could allow for a drag and drop type feeling to represent CI Jobs, Data Deployments, Comparisons, etc. Users who may be new to a DevOps environment would pick up the process quicker allowing them to quickly adapt to the tools and this type of deployment mentality.

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  12. Output information after CI Job regarding problem analyzer skipping some component deployment

    I would like to get some information from the problem analyzer after a CI Job completes as it seems like if it detects a problem during the job it skips deploying some of the components, like user permissions.

    5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  13. Store formatted JSON in source control

    The SFDC metadata API returns some items types as JSON compressed to a single line. For example, this applies to Wave dashboards (.wdash files).

    Gearset neatly expands this to a more readable when visualizing and comparing.

    However, in source control Gearset stores them in their original one-line compressed format. As a result, when doing merging and conflict resolution at the source control layer, these items are impossible to handle, as *any* change (whether technically conflicting or not) results in a conflict from git's point of view.

    It would therefore be great if Gearset kept the expanded format for JSON data…

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. Optional ability to provide a warning when targeting a deployment to a Non-Developer Production Instance

    I'd love to be able to have an extra "warning" message when targeting certain orgs when clicking the "Deploy" button. The thought is that it provides an extra level of confirmation when targeting production, to help avoid mistakes. This could be an optional custom warning message set on a connection that if populated, a "Deployment Confirmation Message" is shown.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  15. Queue Deployments

    **Current State:**

    A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org

    1st Dev deploys work to .dev

    2nd Dev deployment fails because org is locked

    **Idea:**

    A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org

    1st Dev deploys work to .dev

    2nd Dev deployment is queued up, 2nd Dev will be notified via email/browser when queued deployment has started

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  16. Give Permissions to Edit Automated Job Settings

    Adding a feature to give users permissions to edit & delete Automated Test Jobs would be great. Today I had to hunt down a colleague to be have him edit his job when all I had to do was change the schedule. This feature would have saved a lot of time.

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Testing  ·  Flag idea as inappropriate…  ·  Admin →
  17. Validation Failures - Show Error in Table

    In the new UI for Validation to view failed test classes error messages you must click into each failed class to view the details.
    --
    The previous UI showed "part" of the error message within the table. This was extremely useful in identifying all of the "unique" errors that are occurring.
    --
    IE: If 58 test classes fail from "4" unique issues -- then in order to determine that you may need to click into all 58 test classes or fix one at a time --> refresh --> validate.
    --
    This is just a time save feature.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add the open PR feature (Github) to work with BitBucket after a successful commit

    It would be great to add the open PR feature (Github) to work with BitBucket after a successful commit.

    Super helpful for the admin team to close off their feature branches and move onto the next job at hand without having to interact with BitBucket.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  19. Provide reporting capabilities for Deployment History

    Our executive sponsor for Gearset has asked me to provide him with some metrics around our Gearset usage. Specifically, we would like to be able to have access to some of the data that already exists in the Deployment History section, but in a format where we could report on it. Ideally, we'd be able to show how many deployments to production, how many components deployed in those packages, frequency of production deployments in a given timeframe, etc.
    This would be a very valuable feature for us so that we can ensure our executive leadership team is briefed on the…

    4 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  20. Reordering of XML file

    At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base