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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. More granular permission settings for sub groups of a large team

    Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
    For example not being able to connect to/make deployments to 'production' orgs.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  2. User Last loggged in and User Usage

    It would be great to see when a team member last logged in on the user account management page. It would also be great to see like a report or extension on the user page where we can see user usage information. Like number of compares, deployments, etc.. may when last compare was done.

    13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Manage multiple Gearset teams from a single Gearset account

    I want to be able to Manage multiple Gearset teams from a single Gearset account, and not have to log out and log in again.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Show Read Only Source control Settings to Members

    Would be good to see the current settings of Source control for Members in read only mode.
    Currently what greats us is just a text message:
    "Only team owners can change these settings."

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Account owner should be able to delete templates created by others

    If a team member is removed from Gearset team, any template or previous activity can not be removed by anyone else. Leaving some clutter behind. It would be good to have the Owner of the Gearset account/team to have a super admin level access to all templates/data created by other team members so clean up could be managed....

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Documentation around ramifications of deleting a connection (and possibly an Archive option)

    I haven't seen anywhere in the support documentation that details any ramifications (if any) when deleting a no longer needed Salesforce connection in GearSet.

    The kind of ramifications I'm thinking about are:


    • Validated Packages based on the connection, could I still review/clone/deploy?


    • Deployment History - will all information still be available? Can I still clone from a previous deployment?


    • Comparison History - can I pull up a previous compare?


    etc.

    If there is any negative impact to the above, then it would be appropriate to have an "Archive" option for Salesforce connections. The thought with this would be one, the…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Ability to hide other team members' personal filters

    My team is working on different projects at the same time, often times independently from each other. The ability to hide all filters personal filters that aren't my own (and maybe selectively share them with a select few team members) would be greatly appreciated!

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  13. edit other team member's CI job

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

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Naming Org Pairs

    I'd like to be able to name 'Pairs' of orgs so I don't have to re-select them, like 'DEV to UAT' or 'HOTFIX to Production'

    35 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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!

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  19. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base