Enable FF for Content Editor in issues for members of gitlab-org

Goal

In MVC: Allow using the Content Editor in issues b... (#371931 - closed) we explored what it would take to make the Content Editor available when editing an issue. The successful MVC and further iteration on the functionality of the Content Editor to support autocomplete suggestions and quick actions puts us in a place where we are ready to dogfood the editor within GitLab.

Proposal

Enable the content_editor_on_issues feature flag for all members of gitlab-org and solicit feedback so we can understand the remaining gaps in experience and expectations.

Details

1. We don't have to make this available in the New Issue view. The work items initiative will eventually make that view irrelevant so we shouldn't bother at this point.
2. There are some concepts for updating the visual styling to better fit into the issue editing vision, the Plan team will explore implementing a property of the editor that can toggle the UI to suit their use case rather than wait for us to update the UI of the entire component.
3. Feedback will be gathered in Feedback: WYSIWYG Markdown editing in Issues (#379045)

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.