I think where a task is displayed in a "box" in the UI, it displays ID, title, priority (through color-coding) and associated project(s). For completeness, if the task is in a work board, it should show the column name as well.
Since a task might be in multiple projects, one way of doing this would be to replace the "project" bubbles by "project {SEPARATOR} column" bubbles.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Wontfix | epriestley | T6579 Display hovercards on Tokens in Typeaheads | ||
| Duplicate | None | T6634 Typeahead default should maybe be more than 5 | ||
| Resolved | epriestley | T3670 Add subprojects | ||
| Wontfix | epriestley | T5100 Show work board column names as part of task basic information in query results and reference link popups | ||
| Resolved | btrahan | T5090 Allow projects to change their icon in typeaheads | ||
| Resolved | btrahan | T4739 Change typeaheads to use FontAwesome instead of old icons | ||
| Resolved | epriestley | T4693 Leverage new timeline design to optimize growth metrics | ||
| Resolved | None | T4420 Modernize typeahead datasources | ||
| Restricted Maniphest Task | ||||
| Resolved | epriestley | T4807 Workboards should support alternate ordering rules, including "don't keep arranged by anything" | ||
| Resolved | epriestley | T5476 Move workboard relationships to a dedicated (non-edge) table | ||
| Resolved | btrahan | T5245 Migrate Maniphest Projects to use edge infrastructure |
I guess column name should also be reflected in the popup that appears when mouse hovering on a task link if that's not already the case.
After T5090, I'd like to try to make these elements tall enough to include the icons, which I think will help reinforce differentiation between project types. We could look at adding columns at the same time.
However, it would be nice to do this without significantly impacting the amount of vertical space a task item requires.
(On mobile, we could hide the columns; I'm not sure if seeing more tasks or seeing more columns is likely to be more important. See also T3574.)
We also might need to move the column relationship off of Edges infrastructure -- it's an odd three-point relationship (task, project, column) and I think some of the queries end up doing a lot of work right now.
T4807 may motivate switching off edges, too, since it implies we need new order storage for the "don't arrange by anything" view.