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

30 results found

  1. Support integration with OKTA

    Salesforce orgs that have OKTA as a SSO Identify Provider cannot seem to be connected to Gearset using SF Authentication. Therefore is makes it impossible to do Monitoring and Tests.

    Please look into supporting OKTA SSO

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

    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)
  3. Offer source branch update as option to trigger CI from custom Git (Gitlab in my case)

    Please allow to select "when source branch updated" option in the CI jobs section when the source is a custom git repo

    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)
  4. Upload Manifest File When Creating Scratch Org

    When spinning up a SalesforceDX scratch org, allow a manifest file to be included. One use case is for when the Dev Hub org has PersonAccounts enabled and that feature can be enables upon creation of the scratch 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Improve formatting of the XML pushed to git

    Is it possible to improve the formatting of the XML?
    The XML returned from MavensMate is formatted better.

    It's mainly just missing new-lines.

    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)

    We’ve made a bunch of improvements to the XML formatting this year, including tidying up which namespaces are included and having more consistent indentation and newline behaviour.

    As always, we love feedback on the changes we’re making so please submit another idea if there is still improvements we can make in this area!

    Thanks,
    Kevin

  6. Support auto-complete in the dropdown for Source Control repos

    Would it be possible to provide an autocomplete dropdown when selecting the git-repo? Similar to selecting the Salesforce-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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Allow user to choose the folder in a git repo that contains metadata

    Improve git access by allowing the user to define folder where metadata is stored in a git repo.

    We are not keeping directly content of src in git branch but src folder because we have there also few other folders.

    The problem is that if I try to compare sandbox with git then I am getting results that all files are new.

    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. CI Job notification email should report the actual errors directly instead of linking to CI Dashboard.

    This potentially can help the team to collaborate on the errors directly on Teams messages.

    For example, at present, the MS team notification says [A continuous integration validation job failed for validation job for PR # xx], but doesn't say which CI job name or what the validation/deployment error was.

    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)
  9. Remember default Bitbucket Server repo

    According to https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/17292778-remember-a-default-github-repo, when one uses GitHub as a git provider, Gearset will remember the last used repo in a comparison.

    However, this is not the case with the Bitbucket Server integration. Every time I do a comparison, I have to select the repository and branch again. With a large number of each, this is very tedious.

    Please remember the last-used repo as a default, and do the same for the last used branch on that repo.

    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)
  10. Clickable Jira Request within Deployment Report

    I would like the ability within the deployment report to make the jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.

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

Feedback and Knowledge Base