Skip to content

signal descriptions are very long #1572

@adboio

Description

@adboio

problem

"problem" is subjective, but many of the signal reports have very long descriptions, priority reasoning, and actionability reasoning. it takes me too long to gather enough context to decide if want to do anything with the report

example:

Image

suggestion

  • can we generate a quick one-liner to use as the primary subheader?
  • priority and actionability tend to be very similar to each other, and to the description; they are hidden by default but expanding them still feels overwhelming - maybe we can have a "lite" version of each?

Metadata

Metadata

Assignees

No one assigned

    Labels

    EnhancementNew feature or requestInboxissues related to signals inbox

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions