Skip to content

Follow-up from "Create new related work items on new work item page"

Summary

In !173840 (merged) there were a few things that were noticed regarding the recently added functionality in work items to create related items from the action menu. The details are captured below:

The following discussion from !173840 (merged) should be addressed: !173840 (comment 2229537832)

@nickbrandt mentioned:

  • In the design, it suggests having the actions menu item titled "New related item", rather than specifying the type. I believe this is because we want to allow a user to be able to define other types during the creation process, and so this helps indicate it doesn't have to be the same object type.

    current proposed
    Screenshot_2024-11-26_at_6.52.21_PM Screenshot_2024-11-26_at_6.54.23_PM

  • Related to the above item, there is currently no Type selection when creating a related item from an Issue (or Task). For Issues, the legacy experience actually lets you change the type when creating a related issue (however it does break the linked relationship for some reason 😅 ), and I believe the intent is we want to allow users to select other available types within the selected context (Project). Perhaps this won't be possible currently with Incidents not being work items? Though I would expect we would want to allow this for switching between Tasks/Issues. I understand for Epics it may make sense to not show a Type selection (and instead specify in the actions menu item "New related epic", since that would be the only available type selection. @nickleonard do you have thoughts on this?

    Example on legacy Issues Screenshot_2024-11-26_at_6.48.00_PM

  • Regarding the checkbox that we show for the relationship:

    • It currently isn't treating the ID as a link, where the design indicates we treat it as a link as in the legacy experience.
    • The ID is always showing the longer full path, where we have previously used the ID only since you are creating this from the context (Group/Project) that the related item exists.
    • We should show the type here in lowercase (rather than capitalizing), since that's how we handle it in other areas such as system notes.
    • It's currently missing the Help text shown in the design and from the legacy experience.
    current proposed
    Screenshot_2024-11-26_at_7.17.24_PM Screenshot_2024-11-26_at_7.16.54_PM

  • There is an issue where creating a related item from the drawer doesn't allow you to click the link in the Toast to view the new item (probably more a problem with the drawer behavior). See capture below.

    Screen capture create-related-drawer

@nickleonard mentioned:

@nickbrandt @jachapman The end state I would envision being "Add related item", which initializes the form as a copy of the current item (see Work item create — Pre-populate from origin whe... (#500902)) including the same location and type. Users can then change the location or type, where type is tied to the location.

For epics this was something we had to limit based on current capabilities, i.e. users can't select 'issue' until post-migration. Allowing just epics or tasks, but not issues, would be unexpected.

With issues I could see allowing issues, epics, or task creation, though that's beyond parity so not an issue blocker. Losing incidents doesn't seem problematic from a legacy parity perspective as, as you note, adding a related incident doesn't actually work in the legacy flow.

Edited by Nick Brandt