-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add notes to outgoing and incoming messages #7302
Comments
+1, this is something I've wished we could do for quite some time. Another use-case would be the "the authority responded with a link to download the file - we've put it on our fileserver" messages that we currently apply as annotations. These are done with the best of intentions, but can get lost in a thread containing multiple messages, so it'd be helpful to put them in the viewer's eyeline as they are reading the relevant message. |
+1 This could also help us to note admin actions, particularly if we get #1005 |
Quickly stubbing this out in web inspector to see how we might position it: Between the header and <aside id="notes">
<div class="correspondence_text">
<p>Foo bar baz Foo bar baz Foo bar baz</p> Within the <div class="correspondence_text">
<aside id="notes">
<p>Foo bar baz Foo bar baz Foo bar baz</p> |
This issue has been automatically closed due to a lack of discussion or resolution for over 12 months. |
It's good to be able to be as precise as possible with our admin actions. For example, we try to minimise information removal by applying the least destructive approach possible (censor rule -> prominence of individual attachment -> prominence of individual message… and so on).
By the same token, it would be useful to add an explanatory note to a specific message rather than the whole request.
The context here is that I'm looking at an incoming issue from an authority saying they've released inaccurate material by mistake. They've followed up with a replacement. It would be good to use the directly attached/note via tag approach to mark this as "inaccurate" but not something we'll remove.
SEO: notable, noteable, tag based notes.
The text was updated successfully, but these errors were encountered: