2020-02-10 - Triage report for "group::ecosystem"
Hi, @deuley @nhxnguyen @lvanc
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- #38126 Jira integration menu from UI should allow testing a configuration set via API Category:Integrations, ~"Jira", UI component, customer, devopsenablement, feature, ~"group::ecosystem", ~"services"
- #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. auto updated, customer, devopsenablement, feature, ~"group::ecosystem", potential proposal
- #16182 Integrate with Jama (requirements management software) Category:Integrations, auto updated, customer, devopsenablement, ~"external services", feature, ~"group::ecosystem", potential proposal
feature (non-customer)
Unscheduled- #198647 [For Gitlab.com / Non administrator plans] API endpoint to get all membership (projects and groups) of a given user, on the projects/groups owned by the user making the API call. api, devopsenablement, ~"enhancement", feature, ~"group::ecosystem", to schedule
- #198639 Feature proposal: Change comment tab target in Jira issue Category:Integrations, ~"Jira", devopsenablement, ~"enhancement", feature, ~"group::ecosystem"
- #196981 GitLab Workfront Fusion Integration Category:Integrations, devopsenablement, feature, ~"group::ecosystem"
- #196170 (closed) GraphQL query to get all projects and groups a user has access to ~"Category:APIs/SDKs", Category:User Management, GraphQL, api, devopsenablement, feature, ~"group::ecosystem"
- #42465 (closed) Docs feedback - feature proposal: Write your title devopsenablement, feature, ~"group::ecosystem"
- #39125 (closed) Investigate backend architecture for mass-integration Category:Integrations, backend, devopsenablement, feature, ~"group::ecosystem", ~"workflow::In dev"
- #38117 Ability to ignore work in progress merge requests for mattermost notifications devopsenablement, feature, ~"group::ecosystem", mattermost, notifications
- #37785 JIRA integration: add a black list of names that are not Jira issues devopsenablement, feature, ~"group::ecosystem"
- #37373 Jira Integration commits should populate a custom field or link instead of comment ~"Jira", devopsenablement, feature, ~"group::ecosystem"
- #36302 (closed) First-class Jira Integration Alliances, Category:Integrations, ~"Jira", devopsenablement, feature, ~"group::ecosystem", meta
- #36148 (closed) Group and / or global integrations devopsenablement, feature, ~"group::ecosystem", ~"webhooks"
- #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"
- #32601 (closed) Integrate GitLab with DeepCode Category:Integrations, devopsenablement, ~"external services", feature, ~"group::ecosystem", potential proposal, product discovery [DEPRECATED]
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 | 1 | 0 | 0 | 0 | 0 |
~P2 | 0 | 1 | 1 | 0 | 0 |
~P3 | 0 | 2 | 10 | 1 | 0 |
~P4 | 0 | 0 | 14 | 5 | 0 |
~"No priority" | 0 | 0 | 1 | 1 | 7 |
Unscheduled ~bug (non-customer)
- #200056 (closed) Markdown-enabled ChatNotification for non-markdown content should escape special characters Category:Integrations, ~"Teams", backend, ~"bug", devopsenablement, ~"group::ecosystem"
- #198302 (closed) 500 Error testing for Webhook Category:Integrations, ~"Jira", ~"bug", devopsenablement, ~"group::ecosystem"
- #196386 (closed) gitlab to jenkins job webhook test failing with 404 Jenkins, ~"bug", devopsenablement, ~"group::ecosystem", ~"webhooks"
- #196027 (closed) Web hooks - Merge Request "update" action doesn't contain required changes in the payload ~"bug", devopsenablement, ~"group::ecosystem", ~"webhooks"
- #195533 (closed) Docs feedback: unclear what is meant with %{environment_filter} in promQL queries Category:Integrations, ~"S3", ~"bug", devopsenablement, documentation, ~"group::ecosystem"
- #195179 (closed) Transient failure in qa/specs/features/ee/browser_ui/3_create/jenkins/jenkins_build_status_spec.rb Jenkins, ~"P1", ~"Quality:flaky-tests", ~"S1", ~"bug", devopsenablement, found:master, found:staging.gitlab.com, ~"group::ecosystem", ~"missed-SLO"
- #39174 (closed) Generic Alerts Endpoint has empty template in Admin Area Category:Integrations, ~"P4", ~"S4", ~"bug", devopsenablement, ~"group::ecosystem"
- #39151 (closed) Slack Application Integration fails after path reaches 100 characters Category:Integrations, ~"Slack", UX, ~"bug", devopsenablement, ~"group::ecosystem"
- #38307 (closed) Saving settings for Mattermost Notifications integration displays error Category:Integrations, ~"bug", devopsenablement, ~"group::ecosystem", mattermost
- #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"
Heatmap for ~missed-SLO bugs
~S1 | ~S2 | ~S3 | ~S4 | |
---|---|---|---|---|
~P1 | 1 | 0 | 0 | 0 |
~P2 | 0 | 0 | 1 | 0 |
~P3 | 0 | 0 | 0 | 0 |
~P4 | 0 | 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.