2019-10-14 - 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-
#14739 JIRA integration - allow to configure Transition IDs per project Category:Integrations, Category:Source Code Management, Enterprise Edition, ~"Jira", UX, customer, devopsplan, ~"enhancement", feature, ~"group::ecosystem" -
#13423 (closed) Allow configuration of unreachable Web URLs for the Jira integration Category:Integrations, Enterprise Edition, ~"Jira", UX, customer, devopsplan, ~"enhancement", feature, ~"group::ecosystem" -
#14229 (closed) Fill additional JIRA fields based on commit message Category:Integrations, ~"Jira", Manage [DEPRECATED], customer, devopsenablement, feature, ~"group::ecosystem"
feature (non-customer)
Unscheduled-
#33317 (closed) Private messages on service desk issues devopsenablement, feature, ~"group::ecosystem", issues -
#32601 (closed) Integrate GitLab with DeepCode Category:Integrations, devopsenablement, ~"external services", feature, ~"group::ecosystem", potential proposal, ~"product discovery" -
#32434 Show GitLab activity on the GitHub activity page Category:Integrations, Github, devopsenablement, feature, ~"group::ecosystem" -
#31397 (closed) Support go-source meta tag for godoc.org devopsenablement, feature, ~"group::ecosystem" -
#30813 GitLab for Gmail addon Category:Integrations, devopsenablement, feature, ~"group::ecosystem" -
#30763 GitLab Integration for the Cypress Dashboard Category:Integrations, devopsenablement, feature, ~"group::ecosystem" -
#30537 Upgrade mattermost integration (add icon_url) Category:Integrations, ~"Ecosystem [DEPRECATED]", devopsenablement, feature, ~"group::ecosystem" -
#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 -
#18731 Support JIRA when creating a new issue from a failed job Category:Integrations, ~"Jira", Plan [DEPRECATED], ~"Verify [DEPRECATED]", devopsenablement, feature, ~"group::ecosystem", issues -
#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"
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 | |
---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 |
~P2 | 0 | 0 | 0 | 0 |
~P3 | 0 | 1 | 8 | 0 |
~P4 | 0 | 0 | 13 | 4 |
customer
Unscheduled ~bug with-
#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)
-
#32845 (closed) JIRA service template shows incorrect JIRA links in existing projects Category:Integrations, ~"Jira", ~"P4", ~"S3", UX, ~"bug", devopsenablement, ~"group::ecosystem" -
#29618 (closed) Cannot connect repository to packigist ~"P4", ~"S4", ~"bug", devopsenablement, ~"group::ecosystem"
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: