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. UI Change: On any pop-up page using Source Control, auto-expand to show Create Branch button

    On a monitor job (and probably elsewhere), clicking "Deploy To" and then selecting Version Control target, you get a default branch, typically master. If you click the link to Create a new Branch from Master - you input the name of your new branch, but the Create Branch button is hidden below the display and you need to scroll down to show it. The Start Comparison button is where the Create Branch button should be, so you end up starting your comparison instead of creating the branch first. Suggesting to change the pop-out window to expand to show both buttons…

    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)
  2. Show Formula Comparisons line by line

    When comparing formulas (in validations, formula fields, workflow criteria...) the comparison should be done line by line.

    Considering the whole formula a block and only showing that "something" has changed in the formula is not useful when looking for conflicts between environments.

    When pushing changes between environments, admins are checking to make sure they are not overwriting other changes with their update. They most probably know the formula has changed (that was their job) but they need to ensure no unwanted changes are added/deleted from the target environment.

    In long formulas with many lines (potentially >100) it's not easy to…

    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)
  3. Revert with one click all changes from this PR

    Please allow reverting PR from lower environments. In mine example, we had a feature that went through develop and uat and was waiting in the pipeline to be added to release but the business changed its mind and canceled this whole feature.

    Please add an option that with one click we can revert PR and changes from lower environments.

    Image:
    https://www.dropbox.com/s/ohvymcs16p9n5ge/2022-06-30_14h10_44.png?dl=0

    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  ·  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)
  4. Notify GitHub that checks are running sooner

    When a PR in GitHub is being validated, Gearset doesn't let GitHub know that the check is happening until after it has run the comparison between GitHub and the target org. Then the check is pending while the validation runs in Salesforce.

    This means that there is a delay between when you create a PR and Gearset's check appearing as pending in the PR. At that moment, it looks like there are no more checks to run in GitHub so you can go ahead and merge. But, you really should wait until Gearset has compared and validated the changes.

    It…

    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)
  5. Create a pop-up warning when on the Selected Items tab before you can deselect all items

    Without the Undo feature, there is the odd time (nightmare situation) where you haven't saved your compare and are on the Selected Items tab and accidentally deselect all items. It would be great to get warned that all work will be lost unless it's saved or the deselect action is canceled.

    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)
  6. Unify the message when you authenticate an org with a username that has been shared. It uses the term "delegated" instead of "shared"

    Unify the message when you authenticate an org with a username that has been shared. It uses the term "delegated" instead of "shared". This could be confusing.

    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)
  7. Delete GitHub webhook when the CI job is deleted

    When we create a CI job where the source is GitHub, Gearset can automatically create a webhook for us in GitHub.

    Would it be possible to delete that webhook in GitHub when we delete the CI job from Gearset? I've got some GitHub repos with failing webhooks due to CI jobs I once created. Obviously, I can tidy up manually from GitHub, but it would be nice to have the option of Gearset doing it for me. The URL seems to be unique to the CI job, so I can't see it having any negative consequences.

    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)
  8. Saved Comparisons should be visible to team members

    I have a team that has access to Gearset but unfortunately they cannot view the Saved Comparisons I've created. To reduce unnecessary time spent on creating and maintaining Saved Comparisons, it would be greatly appreciated if the Saved Comparisons could be shared with the team and possibly allow the owner to delegate access to the Saved Comparisons.

    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)
  9. Run Flow tests during test monitoring jobs

    With the new flow tests, it would be nice if we could also have these run within test monitoring jobs.

    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  ·  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)
  10. to let us configure the default metadata filter by deployment pipeline configuration

    Can we please have a possibility to configure the "standard" metadata filter by each deployment pipeline project?

    I think it is currently preselected by the last used metadata filter from the standard comparison.

    As we usually have a specific metadata filter configured by deployment pipeline project, it would be great that we can configure each project with a default one..

    Thank you!

    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  ·  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)
  11. Test salesforce connections in mass to highlight which need to be re-authorized

    Having a way to monitor/test all salesforce connections in mass to then highlight which need to be re-authorized would be helpful instead of catching them when preparing to do a comparison.

    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  ·  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. 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)
  13. 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)
  14. 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)
  15. 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…

    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. 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)
  17. Allow page layout field additions and removals to be selectable

    As a user, when selecting page layout changes to include in my deployment, I would like to include only the fields I have added that are different from my destination environment.

    Dev environments can be worked on by different people. There are times when a solution requires adding an existing field to a page layout to solve your user story.
    At the same time, another user story may also be making changes to that page layout using different fields (removing or adding).

    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. 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)
  19. 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

    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  ·  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)
  20. 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:…

    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

    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)
  • Don't see your idea?

Feedback and Knowledge Base