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
  1. Sort Validation Only CI Jobs

    In the CI Job page, you can sort the top-level jobs by different columns (Job Name, Source, Target, etc...) but you can't sort the actual instances of that job.

    We can get up to 30 PRs that are all being validated, and it would be nice to be able to sort them in some controllable way. It seems to rearrange them in whatever way it feels.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Be Able to deploy Portal Sharing Settings and Organisation Wider Default Sharing Settings at the same time

    For example if attempting to deploy
    OWD permission Read -> Private, and Portal Sharing Set None -> Read. Gearset will fail validation due to SF complaining that Portal Sharing Settings cannot grant Read permission, since OWD is already giving that access.
    Though what SF sees is that Portal Sharing Set is trying to give Read when it already has that access.

    Therefore, if I want to make the deployment then I would have to do in 2 steps.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Allow delegated users to edit environment variables

    My user is setup on our CI and I have a number of environment variables setup on Custom Labels for ID's.

    Whilst this works great the main issue is if I am Sick/On Holiday there is no way for someone else to go in and add/edit the environment variables thus making me a single point of failure/Reference.

    What would be great would be either have Environment Variables setup at a CI level and delegated users have the ability to go in and edit/create new ones against the CI (This would ensure only those that know what they are doing are…

    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  ·  Flag idea as inappropriate…  ·  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. Inline editing of metadata

    https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/38358922-inline-editing-of-metadata

    The idea above was "closed" due to Environment Variables.

    That feature is too fiddley for our use case as the change that needs to be performed is not consistent. Furthermore, that feature does not help with handling merges.

    Gearset has some merging capabilities, but it only allows to select one file or another, instead of merging changes from both files.

    I'm aware it is possible to perform merges from source control, though it would be easier to train our team if they did not have to learn another technology. Furthermore, it leaves the process to more faults as the…

    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)
  5. Allow Data Deployment to handle more complex structures

    Currently, user is able to select Obj A, Obj B that references Obj A, Obj C that references Obj B. And, in the next step of data deployment it allows user to select Objects where Obj A, B or C, and objects references by those objects.

    If we ignore above example, I want to be able to select: objA(id), objB(id, objA), objC(id, objB, objD), objD(Id), objE(Id, objD). Where the first object I select and everything else is filtered on is objA.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Possibility to validate a feature branch as a whole without having to select the Metadata type

    It looks like the current validation jobs setup in Gearset needs the Metadata Type to be explicitly selected to perform the validation. This should ideally be optional and there should be a capability to just validate everything that is there in the feature branch against the target org. It's really annoying for us that we have to select the Metadata Types to be validated.

    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

    1 comment  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  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. Salesfroce Automation testing

    It will be great if gearset implements salesforce automation tools like Selenium, Accelq, Testim, opkey ect.

    The customer will have all the tools together( deployment, data backup, and testing automation).

    Salesfroce Automation testing

    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  ·  Flag idea as inappropriate…  ·  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. Option to set and make use of 'deployment rules'

    It would be great if we can have the option to set and make use of 'deployment rules':

    1 - receive an alert/warning message (in gearset/via email) right before deploying to a selected target environment, for instance - a production environment if certain pre-defined metadata types are included in the deployment.

    use cases: a reminder to run all test when deleting metadata, a reminder to activate a flow on target environment after deployment.

    2 - block a deployment in the following case scenarions:

    a - if the deployment of certain pre-defined metadata types happens within a pre-defined timeframe.

    use case:…

    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

    1 comment  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  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. Integrate with Agile Accelerator instead of just Jira

    Integrate with Agile Accelerator instead of just Jira.
    It would be great if Gearset (and ideally the Pipelines-feature) could integrate with Agile Accelerator.

    Since we're a Salesforce-partner we want to use as many Salesforce-native solutions. That's why we've been happily using Agile Accelerator for many years.

    It would be great if Gearset can also integrate with Agile Accelerator instead of just Jira.
    Right now the Gearset Pipelines feature isn't useful to us, because of this sole reason.

    Thanks for considering this!

    23 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)
  10. Activity Task Event field level security validation in Profile

    Hi Gearset Team,

    I would like to have a metadata validation for profile field level security involving Activity, Task, Event object as they are related to each other in Salesforce.

    For example:
    If we do a retrieve for Activity, Task, Event object along with profile. In the profile metadata it would specify this:
    <fieldPermissions>
    <editable>true</editable>
    <field>Task.FieldX__c</field>
    <readable>true</readable>
    </fieldPermissions>

    However, if there were to be a mistake in the profile metadata and we commit them in version control it is detected as a 'new item' in Compare and Deploy

    <fieldPermissions>
    <editable>true</editable>
    <field>Activity.FieldX__c</field>
    <readable>true</readable>
    </fieldPermissions>

    When we select this new changes and…

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  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. Enable Field Level Mapping for Data Deployments

    Currently there is no field mapping option available for Data Deployment of Objects. This is a big blocker if we want to migrate selective fields data across Salesforce instances.

    12 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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  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. Include Deployment Name on Continuous integration dashboard

    On the Continuous integration dashboard, specifically in the Validation only CI jobs section, there is no way to associate a validation job with the deployment dashboard in Salesforce. We have a validation only job set up to run tests on PRs when they're created. If we get a handful of them all at once, there is a long list of validation jobs running, but we can't tell which one is the one that's actively running. There is no link between the job in gearset and the job in salesforce.

    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

    1 comment  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  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. Make Gearset more responsive via web design

    Currently when doing deployments I have realized when i migrate to a smaller screen that gearset isn't super responsive and sometimes i have to drag it back to my larger monitor. This was really highlighted when I was attempting to deploy some metadata from my phone (mac was updating).
    Please make gearset more responsive so I can deploy from my phone.

    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  ·  Flag idea as inappropriate…  ·  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. Warn if source version is greater than the version of the target org.

    Often, salesforce will deploy the latest API version to sandbox orgs before production orgs. Therefore it's easy to use API version 55 in your sandbox and then get a failure message when you try to deploy it to your production org which is at version 54. Unfortunately, you have to start to validate your deploy before you get this message. This could be a pre-deployment issue that you can notified right away.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Require a Deployment Friendly name

    Add option to require a Deployment Friendly name, similar to the current settings to require deployment notes and Jira tickets

    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  ·  Flag idea as inappropriate…  ·  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. Force-deploy Flow translations with no difference

    At the root of this, the main problem is that if you create a new flow version through the SFDC flow editor interface, the flow will have a new version of the flow translations based on the previous translations.

    But if you DEPLOY a flow, the new flow version is created WITHOUT flow translations at all.

    This would be fine, if gearset would allow us to reliably deploy the flow WITH flow translations, even if the flow translations had "no changes". (Gearset does not allow us to deploy items with no change, and sometimes doesn't even show them in the…

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  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. Provide a better error when "invalid or null picklist values" is thrown.

    "invalid or null picklist values" is thrown and i have too many picklists to figure out which one is the issue. Please provide speicific fields that are causing errors.

    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 →

    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 Time Column to the CI Deployment page

    Due to recent latency issues regarding SF performance issues, I would like to quickly see how long each CI job takes without having to download an individual report for each job. This can either be solved by either:

    1. Adding a field to the CI Deployment page so that I can compare each CI job

    2. Allow me to extract a complete report of all of the CI jobs and open it in excel with the time column so that I can compare the values. I can currently do this from the Deployment history page, however this does not include the CI…

    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  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  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. Introduce Import/Export feature for Custom Filters

    Expose the underlying JSON/XML for Custom Filters so that we can export it, modify it in a text editor either by hand or with python scripts, then load it back into the custom filter.

    For example I have my main CI filter with 50ish metadata types, and every other filter is a subset which I establish by cloning the "master" filter and deselecting metadata types. Whenever I make a change to the master filter I am forced to nuke all the the "detail" filters and recreate them off the master using the above approach.

    So many clicks. My preference would…

    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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  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. Add RecordType support for PersonAccount

    Problem analyzer is always trying to remove my picklist values from any RecordTypes on PersonAccount. I am forced to use a custom "Problem analyzer template" where "Remove picklists from record type" is disabled.

    Suppose I have a field called pickme: Account.Pickme--pc | Contact.Pickme--c it shows up in the record type XML as Pickme--c, and it seems like gearset tries to find a picklist on account with that exact API name, which will of course fail. My ask is that rather than raising an error at this point, GS should repeat this check on the contact object where it would find…

    15 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  ·  Bug  ·  Flag idea as inappropriate…  ·  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