Allow markdown in Vulnerability comments (pipeline security tab dismissal comments)
Problem to solve
While comments on Vulnerabilities from the Security Dashboards support basic markdown, comments resulting from dismissals initiated on the Pipeline Security dashboard are plain text only, making it difficult to read when they are longer or contain items that read better with formatting such as code snippets and long URLs.
Intended users
User experience goal
Vulnerability comments are as full-featured as Issue comments when it comes to supporting markdown and Special References.
Proposal
We should look to leverage components from Issue, Epic, or Design comments. Markdown is most important along with special references for at least MRs, Issues, Epics, and other vulnerabilities. However, quick actions that do not apply such as setting milestones or labels do not need to be carried over.
Further details
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Lindsay Kerr