2019-11-11 - Triage report for "group::ecosystem"
Hi, @deuley @nhxnguyen
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.
feature with customer
Unscheduled-
#35766 Display logging for Jira integration in the UI Category:Integrations, ~"Jira", customer, devopsenablement, ~"enhancement", feature, ~"group::ecosystem" -
#34642 Jira integration authentication via SAML/OAuth Category:Integrations, ~"Jira", customer, devopsenablement, feature, ~"group::ecosystem" -
#25877 (closed) Consider adding fog-azure gem to support Azure's object storage. customer, devopsenablement, feature, ~"group::ecosystem"
feature (non-customer)
Unscheduled-
#35597 (closed) github action plugins devopsenablement, feature, ~"group::ecosystem" -
#35533 ldap automately sign in gitlab devopsenablement, feature, ~"group::ecosystem" -
#35342 [RFC] Mattermost notifications, include feature for gitlab updates ~"S4", devopsenablement, feature, ~"group::ecosystem" -
#34797 Missing System Hook Event for transfering a group ~"Category:APIs/SDKs", devopsenablement, feature, ~"group::ecosystem", ~"webhooks" -
#32601 (closed) Integrate GitLab with DeepCode Category:Integrations, devopsenablement, ~"external services", feature, ~"group::ecosystem", potential proposal, product discovery [DEPRECATED] -
#30319 (closed) Docs - product feedback: Slack integration options ~"Ecosystem [DEPRECATED]", devopsenablement, ~"external services", feature, ~"group::ecosystem", notifications -
#29768 (closed) WIP: Surfacing external content extracted from CI error content Alliances - StackOverflow, devopsenablement, feature, ~"group::ecosystem" -
#29715 GitLab integration with Symphony Alliances, Category:Integrations, devopsenablement, feature, ~"group::ecosystem" -
#29460 (closed) Merge Request Pipeline JIRA ID validation as per JIRA ID valid or not and also ID should be in OPEN/INPROGRESS state to proceed Merge Request pipeline Category:Integrations, ~"Jira", Plan [DEPRECATED], ~"Verify [DEPRECATED]", devopsenablement, feature, ~"group::ecosystem", pipeline -
#19398 Update JIRA settings to include "Issues url" and "New issue url" Category:Integrations, ~"Jira", Plan [DEPRECATED], customer+, devopsenablement, ~"external services", feature, ~"group::ecosystem", settings -
#18387 VisualStudio Integration Category:Integrations, devopsenablement, ~"external services", feature, ~"group::ecosystem" -
#18082 (closed) Improvement to JIRA integration Category:Integrations, ~"Jira", Manage [DEPRECATED], devopsenablement, ~"external services", feature, ~"group::ecosystem" -
#17917 Mention Slack user in SlackService Category:Integrations, Manage [DEPRECATED], ~"Slack", devopsenablement, ~"external services", feature, ~"group::ecosystem" -
#17675 (closed) Slash Commands for HipChat Category:Integrations, Manage [DEPRECATED], devopsenablement, ~"external services", feature, ~"group::ecosystem", slash commands -
#17657 (closed) hipchat pipeline integration should have an option to notify only on changes Category:Integrations, Manage [DEPRECATED], devopsenablement, ~"external services", feature, ~"group::ecosystem"
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 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 1 | 1 | 0 | 0 |
~P3 | 0 | 2 | 5 | 0 | 0 |
~P4 | 0 | 0 | 15 | 3 | 0 |
~"No priority" | 0 | 1 | 3 | 1 | 1 |
customer
Unscheduled ~bug with-
#34331 JIRA integration may captcha the JIRA account ~"Jira", ~"S3", ~"bug", customer, devopsenablement, ~"group::ecosystem" -
#32301 GitLab integration not able to close JIRA issue when transition workflow has screen requiring resolution Category:Integrations, ~"Jira", ~"P3", ~"S2", ~"bug", customer, devopsenablement, ~"group::ecosystem" -
#805 (closed) Jenkins runs two builds for single commit Category:Integrations, Enterprise Edition, Jenkins, ~"P4", ~"S3", ~"bug", customer, default-priority, default-severity, devopsenablement, ~"group::ecosystem"
Unscheduled ~bug (non-customer)
-
#35536 (closed) 404 after importing project by repo URL ~"S3", ~"bug", devopsenablement, ~"group::ecosystem" -
#34845 (closed) Webhooks suddenly stopped working when multiple branches pushed at once ~"S3", ~"bug", devopsenablement, ~"group::ecosystem" -
#34432 Project icon shouldn't be set when login is required Category:Integrations, ~"S4", ~"bug", devopsenablement, ~"group::ecosystem", notifications -
#29618 (closed) Cannot connect repository to packigist ~"P4", ~"S4", ~"bug", devopsenablement, ~"group::ecosystem" -
#15280 (closed) Links in Slack notification for builds can be broken by branch names ~"Accepting merge requests", Create [DEPRECATED], Manage [DEPRECATED], ~"P4", ~"S3", backend, ~"bug", default-priority, default-severity, devopsenablement, ~"group::ecosystem", notifications, ~"services"
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: