### Problem to solve Synchronous collaboration is a critical part of any fire-fight. We are streamlining the number of steps it takes to spin up a conference bridge and engage all required parties by embedding this functionality, using Zoom, directly in an issue. Once a user has started a Zoom call for a fire-fight, they need a way to associate the conference bridge with an issue so team members can join swiftly without requesting bridge links from others. Once the call is over, it can be removed via a quick action as well. ### Intended users [Sasha the Software Developer](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) [Devon the DevOps Engineer](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) [Sidney the Systems Administrator](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> ### Further details This work contributes to the [Incident Management Vision](https://about.gitlab.com/direction/monitor/debugging_and_health/incident_management/) <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Technical Constraints It was recommended by the Zoom reps, that we not pursue the JWT integration path, as they are attempting to move away from that path and it is geared more towards server-to-server integrations that are bound to the specific account. This will require us to look at (the recommended path) OAuth based integration, which will require us to create an app on the Zoom marketplace. Additionally, Zoom has already created an GitLab integration in their marketplace, which they have asked us to maintain the existing functionality to support any users who are currently utilizing the existing integration while we work to implement additional GitLab functionality. They suggested we utilize the `account-level` OAuth integration path, instead of the `user-level` path, as it will allow us to implement a solution that addresses our specific use-cases (tightly integrating Zoom in GL issues), however it will require significantly more development efforts. **NOTE:** we CAN implement a new marketplace app as an interim process, but they would like us to eventually support existing functionality in our new app. There is also some additional complexity in the way that Zoom integrations work that will require more work on our side to support both our Cloud and Self Managed customers with the same integration. ### MVC - Proposal Create quick actions that supports interacting with zoom meetings on an issue directly. 1. **Add Existing Zoom Meeting to an Issue** - ~~User pastes an existing **Zoom URL** into a comment. After the user clicks the "Comment" button, the pinned Zoom embed is added under the issue description and the comment resolves. A system note appears letting the user know that a zoom call has been added to the issue by the user who executed the command.~~ - User adds a Zoom meeting using the `/zoom` quick action. The user is prompted to add the specific Zoom `Meeting ID`. After the user clicks the "Comment" button, the pinned Zoom embed is added under the issue description and the comment resolves. A system note appears letting the user know that a zoom meeting has been added to the issue by the user who executed the command. A system alert appears letting the user know that the meeting has been added to the Issue. - User is only allowed to attach a single Zoom meeting to an issue. If the user attempts to add another Zoom meeting using the `/zoom` quick action, a system alert appear letting the user know that `A Zoom Meeting already exists on this issue.`. 1. **Remove Existing Zoom Meeting from an Issue** - User removes a Zoom meeting using the `/remove_zoom` quick action. Once the user has committed the comment, the the pinned Zoom embed is removed under the issue description. A system note appears letting the user know that the Zoom meeting has been removed to the issue by the user who executed the command. A system alert appears letting the user know that the meeting has been removed from the Issue. 1. **Deprecate the ability to pin embed a Zoom URL in the Issue description** - Right now, users can include a zoom link in the description of an issue and it resolves a button at the top. ~~In the future, we will want users to use the quick actions instead of pasting directly in the description so that they can remove it with a quick action.~~ Any Zoom meeting added to an issue description should not generate a pinned embed at the top of an issue. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references * [Sketch Designs - Zoom MVC](https://sketch.cloud/s/jM1kz) /label gitlab-ce~10230929