### 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. Starting a zoom call from an issue should be as easy as it is in Slack using a slash command so we are going to build a quick action that does exactly that so that users can stay focused on the issue at hand while pulling in teammates to problem solve. ### 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?) --> ### Original Proposal Create quick actions that allow users to interact with zoom calls on an issue directly. There should be a quick action to... 1. Start a zoom call and link it to the issue at the same time 1. Link an already running zoom call to an issue 1. Remove a zoom call from the issue 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. <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> ### WIP Proposal **User starts a call directly from the issue** User types in `/zoom` in an Issue's comments and clicks the "Comment" button. The Zoom call starts, and the pinned embed for Zoom calls is added under the issue description. **User adds an existing zoom call to the 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. When the Zoom call status is no longer "ongoing," the pinned embed button from either steps 1 or 2 is removed from the 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 guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? * Number of times the action is used by a unique user to track adoption * Number of times the action is used overall, segmented by company (to see who is using Zoom), and user to understand retention <!-- 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 <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->