Ecosystem:Integrations 14.8 Planning issue

Top Goals

1. Plan for Key Managed Enterprise Integrations (Slack & ServiceNow)

Why? With backend allocated to security priorities, we want to establish clear, validated designs and a plan for Slack MVC integration requirements. Second, we want to understand ServiceNow's current SNOW to GitLab integration and evaluate opportunities for a GitLab to SNOW integration.

2. 3rd Party / Technology Partner Support

Why? Several new integrations are expected and will require some collaboration:

  • JiHu: Harbor Integration, and others that align with JiHu Markets.
  • TabNine: Would allow us to offer a feature competitive with GitHub's AI Programming tool, CoPilot.

3. Security (engineering allocation)

Why? To ensure our platform is secure and reliable.

4. Integration UX & Process Improvements

Why? Incremental updates to how our users access, enable, and manage integrations contributes to usage/adoption of integrations per user/account.

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.

14.8 UX

  1. Rebuild/refactor the Slack Application (epic) -- I'm currently assuming some UX & refinement will be needed here.
  2. New integrations should be discoverable in the left sidebar
  3. Bug or UX challenges in Jira integration discoverability (Discussion, Issue)

14.8 Backend

  1. Continue under the engineering allocation. https://gitlab.com/gitlab-org/ecosystem-stage/integrations/team/-/issues/72. It is anticipated that the allocation will continue until beginning of February.
  2. MR Reviews (Is this the appropriate place for these? Still trying to evaluate JiHu req's, so this is all up for discussion)

(Note: See JiHu's Planning for Next 3 Milestones here)

14.8 Frontend

This is the list of Deliverable issues, weight 7:

  1. Jira Connect App: break app/assets/javascripts/jira_connect/subscriptions/components/app.vue into multiple components
  2. Connect app: Consolidate known limitations into a single alert
  3. Jira Connect New Branch form: Provide better empty state for project and source branch dropdowns

This is the list of Stretch issues, weight 3:

  1. Use consistent spacing in Jira Issue Detail sidebar
  2. Follow-up from "Jira Connect: show all namespaces when search term length < 3"

14.8 Quality (for Visibility)

  1. api/3_create/integrations/webhook_events_spec.rb | Create WebHooks integration sends a push event
  2. api/3_create/integrations/webhook_events_spec.rb | Create WebHooks integration sends a merge request event
  3. api/3_create/integrations/webhook_events_spec.rb | Create WebHooks integration sends a wiki page event
  4. api/3_create/integrations/webhook_events_spec.rb | Create WebHooks integration sends an issues and note event
Edited by Libor Vanc