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

    14 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

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

    8 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  ·  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.

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

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

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Metadata Filter organization with group or tag management

    It's great that we can set filter visibility now to Only Me or to share with Team. It would be nice, especially for larger teams, to have another way to organize them either with tags, folders, sub teams or groups.

    Example: 1 Scrum Team may have 10-15 filters they maintain and use, and another group of users on a team also have 5 or so they use. Both can see all 20, and this adds up fast.

    Feels like being able to group users together could also have other benefits like mass assigning access to orgs (for deployment, validation, comparison)…

    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

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

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

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

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

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

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Show the name of the draft I am working on

    Would be nice to see the name of the draft I'm working on while I'm working on it. Oftentimes working on multiple things at once, this can get really 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

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  13. Rename drafts after they're created

    It would be really nice to be able to rename drafts after they've been created. Sometimes users will name things differently, and it would be nice to be able to clean this up.

    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  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Microsoft Active Directory authentication for Gearset

    Our company works with Microsoft tools and it would be very useful for us to be able to authenticate with Microsoft Active Directory. That way our security team only has 1 place to manage users for all our tools.

    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  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  15. Ability to lockdown access to delete Deployment history

    It'd be nice if there was a way for admins to restrict access for devs/other users when it comes to deleting items from deployment history. The use case here is when a sprint is done and we're promoting changes from QA to UAT, it'd be nice to select all the sprint packages and combine them from deployment history so a user doesn't have to go through each change at a time. Providing full access to everyone opens the possibility for them to delete a package that should've been bundled with other packages on the promotion to UAT.

    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  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow accessing multiple teams through the same social sign-on (LinkedIn / Google)

    As a consultant who works with multiple clients and has limited access to the production org because of their infosec policies, I cannot create multiple Google/LinkedIn accounts to log on to them, nor continue jumping from one group to the next one.

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

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

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

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

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

Feedback and Knowledge Base