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.

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.

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.

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.

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.

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.

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.

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.

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

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

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?

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.

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?

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.

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

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.

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