2020-02-03 - Triage report for "group::access"

Hi, @jeremy @dennis @lmcandrew @amandakhughes

This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:

Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:

  • Determine if the issue should be closed if it is no longer relevant or a duplicate.
  • If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
  • Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
  • Once a milestone has been assigned please check off the box for that issue.
  • Please work with your team to complete the list by the due date set.

Feature Proposal Section

For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.

Unscheduled feature with customer


Unscheduled feature (non-customer)


Unscheduled UX Debt Issues


Bug Section

For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.

Heatmap for all bugs

Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.

~S1 ~S2 ~S3 ~S4 ~"No severity"
~P1 2 0 0 0 0
~P2 3 9 0 0 0
~P3 0 2 46 6 2
~P4 1 2 35 25 0
~"No priority" 0 10 43 39 86

Unscheduled frontend ~bug with customer


Unscheduled frontend ~bug (non-customer)


Unscheduled ~bug with customer


Unscheduled ~bug (non-customer)

  • #199263 (closed) PersonalAccessTokens::ExpiringWorker fails every time with a date range error Background Processing, ~"Category:Authentication and Authorization", ~"bug", devopsmanage, ~"group::access"
  • #197895 (closed) NoMethodError: undefined method `namespace' for nil:NilClass ~"Category:Authentication and Authorization", ~"P1", ~"S1", ~"bug", devopsmanage, ~"group::access"
  • #197313 Group path validation does not handle subgroup paths properly ~"Category:Authentication and Authorization", ~"S3", ~"bug", devopsmanage, ~"group::access"
  • #196721 (closed) gitlab omniauth + oauth2 report "You need to sign in or sign up before continuing." authentication, backend, ~"bug", devopsmanage, ~"group::access", oauth
  • #196150 (closed) Previous Group Path Exposed via Transfered Group/Sub-Group/Project Audit Events ~"Category:Authentication and Authorization", HackerOne, ~"P4", ~"S4", ~"bug", devopsmanage, ~"group::access"
  • #196131 (closed) SAML - bypass 2 factor authentication - don't require GitLab 2FA to exist ~"P4", ~"S4", ~"bug", devopsmanage, ~"group::access", saml
  • #196028 (closed) Impersonating an admin who impersonates yourself leads to a non-audited authenticated session ~"Category:Authentication and Authorization", ~"P4", ~"S4", ~"bug", devopsmanage, ~"group::access"
  • #195666 (closed) GPG key upload has no effect but also shows no errors ~"Category:Authentication and Authorization", ~"S2", ~"bug", devopsmanage, gpg, ~"group::access"
  • #194189 (closed) Endless automatic omniauth redirect loop if user doesn't exist ~"S2", ~"bug", devopsmanage, ~"group::access", saml
  • #121569 (closed) I keep getting logged out every day! ~"Category:Authentication and Authorization", ~"S4", ~"bug", devopsmanage, ~"group::access"
  • #119497 (closed) Gitlab redirects me to serviceworker.js ~"S3", authentication, ~"bug", devopsmanage, ~"group::access", needs investigation
  • #119291 (closed) Setting a complex password for a newly bootstrapping instances fails ~"Category:Authentication and Authorization", ~"bug", devopsmanage, ~"group::access"
  • #118433 (closed) GitLab CE "500 Error" when i go to group_members page ~"Category:Authentication and Authorization", ~"S3", ~"bug", devopsmanage, ~"group::access"
  • #85046 (closed) Gitlab CE does not send reset password email ~"Category:Authentication and Authorization", ~"S2", ~"bug", devopsmanage, ~"group::access"
  • #55345 (closed) project_count size in /groups/???/-/children.json does not take user access permissions into account and returns the full size. ~"Category:Authentication and Authorization", ~"S3", ~"bug", devopsmanage, ~"group::access"

Heatmap for ~missed-SLO bugs

~S1 ~S2 ~S3 ~S4
~P1 0 0 0 0
~P2 1 4 0 0
~P3 0 0 0 0
~P4 1 0 0 0


This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:


If assignees or people mentioned in this individual triage package need to be amended, please edit team-triage-package.yml.