2019-08-26 - Triage report for "group::gitter"

Hi, @jramsay @zj @timzallmann

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 gitlab-ce~2278648, 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.

Unscheduled feature (non-customer)

  • gitlab-ce#52026 Gitlab/Gitter User Synchronisation gitlab-ce7825516, gitlab-ce3103452, gitlab-ce10230929, gitlab-ce10690822
  • gitlab-ce#30059 Issues with Integrated Chat gitlab-ce7825516, gitlab-ce3103452, gitlab-ce10230929, gitlab-ce3412464, gitlab-ce10690822, gitlab-ce2655208, gitlab-ce~2658854

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: