[go: up one dir, main page]
Skip to content

Work Items - Prevent breaking changes for creating incidents and tickets

Problem

With the creation flow for legacy issues, you can select a type = Issue or type = Incident.

Screenshot_2024-05-17_at_10.29.32_AM

Challenges:

  1. Work item type of issue will use the new creation flow when migrated to work items.
  2. Incidents will not be migrated to work items at this point.
  3. How do we avoid breaking creation workflows for issues and incidents?

Proposal

  • Ensure work item issues and non-work item incidents creation flows are not disrupted/broken.

Implementation Tasks

Lists/boards:

  • Add incidents to create list from issue/work item list (point to legacy incident form)
    • Remove type selection from legacy incident form
  • Support legacy incidents with legacy sidebar in boards (not sure if any work is needed as this is already the case, skip if so)

Work items:

  • Quick action: Add incident to /type (alias /promote_to_incident to /type incident, do not show in list)
  • Type change via UI: Add incident to Change type flow
  • Deprecate /convert_to_ticket quick action and extend the type quick action support params based on type ( /type <typename> <params>, so you could use /type ticket [email: xyz@client.com]). We'd similarly need to prompt the user for the email as part of a confirmation when using the UI type change.
  • Account for is what happens to the work item when it's converted to a legacy incident. I think the best case is that navigating to the original work item URL automatically redirects to the legacy incident URL
Alternate path (Less preferred)

This can be used if extending the "Type" flows — which are meant for work items — to non-work items adds significant effort. Using type is preferred from work items as it means users can consistently use the same flow without understanding why 'incidents' require a different flow.

  • Quick action: Add /promote_to_incident quick action (promote is the wrong term, but it doesn't make sense to change this now)
  • Type change via UI: Add "Promote to incident" action to action menu

Legacy incidents:

  • Quick action: Add /convert_to_issue quick action
  • Type change via UI: Add Convert to issue action
Edited by Gabe Weaver