[MGNLUI-3167] A message is marked as read/not new, if I close its message banner Created: 22/Sep/14  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: app framework, pulse
Affects Version/s: 5.3.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: next, quickwin, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 1 error message banner.png     PNG File 2 banner disappears - but message no longer new.png    
Issue Links:
relation
is related to MGNLUI-3168 Errors are sometimes not marked as "new" Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

When an error occurs, I can close the error message banner by clicking on the "x", but that also marks the message as no longer "new", although I haven't actually read the message. Closing the banner should only do that - close the banner - and not do anything with the message.

The "new" flag of a message should only be removed:

  • if I explicitely open a message in Pulse to read it
  • if I select the message in Pulse and mark it as "read" (not possible currently)
  • if I click on the "[MORE]" link button in a message banner to get to the details of a message (this also opens the message)

We strive for a unified treatment of "new" and "read" (similar to application such as Apple Mail) as the subtleties of "new" vs. "read" messages often lead to confusion and, hence, missed messages.


Generated at Mon Feb 12 09:03:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.