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

34 results found

  1. to give an option to take a backup of Filter's data.

    As an admin, I share my deployment filter with developers to add new item to filter. As many team members are working on the release , there is a possibility of jeopardizing the filter's data. I wanted to take a back up of the filter's items periodically. How can i do this?

    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. Provide controls around who can create/manage Salesforce Connections

    I have a team of multiple admins that use GearSet and I want to fully control who can deploy where. I can set this up with security today in GearSet by what kind of access I grant. However a user can create their own connection using their credentials and get around the shared connections I have established. I would like the ability to disable a users ability to create new connections which would then only allow them to use pre-existing connections that I have established appropriate security for.

    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)
  3. Allow editing Orgs created by other users

    If there is a Gearset user who adds a bunch of orgs, and then quits-- and then a password change is needed for those orgs (or even something simple, such as a nickname change-- it is impossible for another Gearset user to edit the previous Org.

    A workaround is possible to remove the previous Org and add a new Org, but this could lead to lost comparison history, something that many businesses (mine included) care a lot about.

    Can access to edit Orgs created by other users be 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow optional parameters to the GearSet login url to support login method and custom domains if needed

    When using Salesforce logins along with a custom domain, the current gearset login process requires 6 steps:

    1. go to https://gearset.com/
    2. Click "Log in" in upper right
    3. On the "Welcome back screen", click "Salesforce (Production, Developer)"
    4. On the Salesforce Login page, click "Use Custom Domain"
    5. Enter "customdomain" and click "Continue"
    6. Enter Salesforce Production Username and Password

    If the GearSet login URL (from step 2) https://app.gearset.com allowed for optional parameters, a couple of the above steps could be eliminated

    An example URL might be:

    https://app.gearset.com?loginMethod=sfProdDev&customDomain=customDomain

    or

    https://app.gearset.com?loginMethod=sfSandbox&customDomain=customDomain--sandbox.cs11.my.salesforce.com

    Then that URL with the params could be saved as a favorite or placed in…

    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. Add an option to share orgs by default

    Where we have a developer-manager, and a team of developers, it would be useful to be able to have a default for sharing org-connections where the manager always has access to their team's orgs.

    At the moment, we have to share each org one-by-one.

    This has caught us out where a dev team member validated a deployment, then went on holiday thinking that we could deploy it for them. They forgot to share the org-access, so we had to recreate the deployment to get it done.

    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)
  6. edit other team member's CI job

    Have a way to edit other team member's CI jobs, if appropriate permissions are given.

    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

    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 bulk org access for new users, new org permissions upon adding

    When adding a new user having the ability to give the same level of access to all orgs at once would be greatly beneficial.

    Likewise, when adding a new org and having the ability to set user access to the new org would save time as well.

    We are adding new orgs frequently and will be adding users as well. Saving time on permissions would be great!

    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. Allows admins to limit the available branches of a repository

    When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.

    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)
  9. Expand the user security model to restrict user compare / deployment access to defined comparison filters

    Hi guys -

    In many instances, we would like to restrict user access to certain compare / deploy metadata filters. In our case, it would be rare that all metadata changes are to be deployed and we would like to give our engineers access to only certain filters. This would reduce the risk that items that should not be deployed at a high level will not be deployed. In the current model, if a user has deploy access, they can deploy anything and everything. This is what we are looking to avoid.

    Thanks in advance for your time!

    Best,

    Richard

    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)
  10. Ability to pause subscriptions for inactive users

    Manage users on "My Team", so we can activate/deactivate users and then save on licences that are not used until reassigned.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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)
  12. Support grouping of Manage Orgs page

    Support the ability to group org credentials on the Manage Orgs page by a new Group Name attribute. In managing multiple clients with dozens of PRD and Sandbox orgs it would be extremely helpful to be able to group and filter related credentials by client. However, to expand this feature to support multiple use cases, providing a new Group Name attribute (text) which could contain any value would be fantastic!

    Thanks for your consideration,
    Mike

    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)
  13. Allow a deployment team to update the same draft deployment at the same time or warn the end user of a draft in use by another user

    When a dev team work on a shared deployment, it would be nice to work on the same deployment draft, at the same time. At a bare minimum, it would be good to be warned that someone is updating the draft at the same time as 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Manage Orgs Re-authorization returns you to a default sorted list.

    I refreshed a sandbox. I need to re-auth my orgs. I go to Manage Orgs, and sort by my friendly name. I click re-auth, and OAuth is successful and the app tells me I did a good job. But the page it returns me to is using a different sort then I left the page with. ie, it sorts the list by username again. Just extra button clicking I'd like to get rid of if possible. I have to re-auth orgs all the time.

    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