My feedback

2 results found

1. Filter branches by tag name

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Chris Vaughan shared this idea  ·  May 19, 2020

2. More granular permission settings for sub groups of a large team

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Help us improve Gearset » Team and account management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   An error occurred while saving the comment
   Chris Vaughan commented  ·  May 7, 2020  ·  Edit…  ·  Delete…

   Currently, there is no mechanism in place to prevent a user that has credentials from connecting Gearset to a production or UAT org. It would be an awesome feature to lock deployments at the org level in order to prevent users from connecting to sensitive environments within Gearset rather than doing this via permissions in each org.

   Save Submitting...
   Chris Vaughan supported this idea  ·  May 7, 2020