Nick Leonard (b6285b16) at 17 Mar 14:33

Nick Leonard (4da609db) at 16 Mar 21:38

Nick Leonard (0b5d4e8b) at 16 Mar 21:00

Suggested change makes sense to me.

@nickbrandt will be covering this though he's OOO for part of this week, I'll cover a few things in the meantime:

This prevents users from doing a side-by-side copy/paste of content that Duo Chat helped them plan (e.g., issue descriptions, acceptance criteria, task breakdowns) into the new issue form.

@gweaver The ideal flow here would be that the work item gets created from the chat and the user linked to that work item, minimizing the need for copy-paste. Does this fail today? If so, can we understand why? If we're copying the content it seems like the content is correct 🤔

Second, users today can open in full page, which retains the Duo context. This does require a second action but if Duo is typically creating the item automatically I think this would be uncommon.

Looking for UX/design perspective on rendering the new work item page similar to how the work item detail panel is being rendered today.

@acroitor Limitations on panels will make this difficult — for instance if you have a board open, with a work item open in the panel, and you want to create a related item to that work item, we don't support a 3rd panel. Thinking about places we want to enable the use of the contextual "add" flow, there are cases where this could work, namely creating an item from a board and creating an item from the list, as in those cases we can keep the list/board as the main panel and the new form as the right panel, and shouldn't run into problems. If we use the panel in more contexts in the future, as I assume we will, this would make "global add" more challenging as we wouldn't be able to predict how the panel system will behave (e.g. what if I have a pipeline in the left, and a job in the right (hypothetical use), and I want to create a work item related to the job, how do the panels respond?)

I understand how it could be beneficial in some cases but overall I do not think the panel pattern, as currently employed, will support the breadth of needs.