Ecosystem:Integrations 15.5 Planning issue

🧭 Strategic Context

FY22 Q3 OKRs

Product

Maintain 99.95% Error Budget for all three milestones
Increase MAU for Integrations by 30k (target of 487k)
Target 1 new Integration contribution in process

Engineering

Need to capture link from Arturo to these OKRs -- feel free to edit/add if you have it!

💪 Capacity Check

Backend - 22 pts

Frontend - 5 pts (+ ~3-4 in flex support)

Based on Capacity Google Script leveraging PTO by Roots.

⚖ Issue Type Distribution

Type	Distribution
typefeature	55%
typebug	35%
typemaintenance	10%

Based on Issue Types by Milestone.

🟢 Action Required

Please review your current stories and goals, to make sure they are aligned with the Milestone goals. Everyone should go through the stories that are really needed to help hitting these goals reliably towards the end of the milestone.

What should I do? Link Related Stories to the priority discussion blocks below. This might need some investigation to make sure we are not overlooking critical work, and that is acceptable. We can save a lot of time by spending time on preparation.

Key Themes

📺 Kickoff Video

1. Complete Jira Proxy for Self-Managed users of the GitLab for Jira App

Why? We're very close to delivering this, it allows us to move users off of the DVCS integration where they may have been using Jira Cloud + Jira Server/Datacenter, which is not supported. And it will increase usage/adoption of the GitLab for Jira App as this gap has been a common complaint within the GitLab for Jira App page.

2. Expand the GitLab Slack App to support notifications, providing a migration path for users from the Slack notifications integration.

Why? This will consolidate functionality between Slack and GitLab into the latest Slack technology (allowing us to deprecate use of legacy technology). This will unblock Monitor:Respond so they may add Incidents as a trigger for notifications, which means net new customer functionality. And this will open us up to add net new functionality in the future through a consolidated delivery mechanism. Note: we'll need to also add support for Self-managed users before we start adding net new features from our end.

3. Webhook Encryption iteration

Why? Several key customers are blocked by the security concerns of users able to view webhook URL details that may contain sensitive information. The combination of the GitLab permissions model and the limited masking options gives users few options for handling this gracefully. Iteration here will give our customers more confidence in using webhooks within GitLab.

4. Automated API Docs Generation

Why? This will support our API WG and high customer demand around using our APIs programmatically via OpenAPI spec, it means having up-to-date documentation consistently, and it supports the FedRAMP initiative as our internal teams can use the OpenAPI spec for DAST API Scanning.

UX

This is the list of Deliverable issues:

Backend

This is the list of Deliverable issues, weight 24:

This is the list of Stretch issues, weight 6:

Milestone Prioritization updates:

(Scope creep, prioritization changes)

Based on feedback from the release of Automatic Disabling of Failed Webhooks, we prioritized two new issues for %15.5:

Frontend

This is the list of Deliverable issues, weight 7:

This is the list of Stretch issues, weight 7:

🚀 Release Issues (Release Posts, Documentation Tasks, and Feature Flags)

Theme	Status	Status Description	Release Post
Automatic Disabling of Webhooks	🍎	Still in Dev, unlikely to be ready for release
GitLab for Jira App (Self-Managed Support)	🍎	A FedRAMP issue took precedence, capacity issues, scope creep	Self-Managed Support Extended to GitLab for Jir... (gitlab-com/www-gitlab-com!110680 - merged)
Webhook Encrypted Tokens	🍎	New blocking issues (UX, Backend)

Edited Oct 14, 2022 by Grant Hickman