Use generic state icons for all planning objects
Proposal
In any place where a type-specific icon is used to denote state, replace with a status-only icon and, if not already present, add a type icon.
Why?
As we strive to create a unified, consistent approach to planning objects — and expand the types of planning objects e.g. OKRs — using more reusable iconography will allow us to not only scale in a consistent way but also help users by identifying one common icon rather than many icons with similar meaning.
In particular in contexts where items of different types are mixed, such as linked items, this will ensure users can scan for "status" in a consistent manner, rather than scanning type+status combined.
This further gives "Status" more prominence as a highly important workflow detail, and aligns with future work for extending status.
Where these icons are used
-
Detail page headers ( !135272 (merged)) -
Popovers ( !135272 (merged)) -
Epic > Child items and epics -
System notes (reopen note only)