Make list controls usable in all GLFM contexts

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Opportunity

Currently within work item descriptions users can reorder, delete, or convert checklist items to child items, extending the edit capabilities of checklists beyond just check/uncheck without having to open the editor.

To provide a consistent experience we should make these controls available in any GLFM context. Move and delete will always be applicable, "Convert to child item" would not but we could consider a "Create issue" option that could apply more broadly, e.g. from an MR.

Proposal

• Move checklist logic out of work item description, into GFM rendering so it's always available
  • Still requires permissions checks, e.g. user must be able to edit the GFM content.
• "Convert to child item" remains conditioned on the context having available child item types, should not appear on tasks, MRs, commits, etc.
• Add a "Create new issue" item available in all contexts
  • Opens "Create work item" modal. Project should be set to the current project, if work items are available; if not, set to first in list. Type defaulted to issue.
  • Follow same patterns as "Convert to child item" for using checklist content for title (and description, if more content is present)
  • On save:
    • Do not remove checklist item. Link the checklist item text to the created issue.
    • Show a toast "<work item type> created. View details". Do not navigate away.