[MGNLUI-3168] Errors are sometimes not marked as "new" Created: 22/Sep/14 Updated: 11/Sep/15 Resolved: 11/Sep/15 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | app framework, pulse |
| Affects Version/s: | 5.3.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Andreas Weder | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | next, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| 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
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
It seems that sometimes, error messages logged in Pulse are not marked as "new" and thus, confusingly, do not increase the message count. All incoming messages should always be marked as "new" and have an effect on the message count. |
| Comments |
| Comment by Andreas Weder [ 22/Sep/14 ] |
|
This was reported by Jan; I did not attempt to recreate the exact circumstances under which this occurs. I'm linking an issue, which could be related or maybe even causing this. |
| Comment by Jan Haderka [ 22/Sep/14 ] |
|
not 100% sure, but I think as soon as I click on the message trying to see [more] it's already marked as read ... same as in case of closing the error bar w/o looking at the message as described in |
| Comment by Andreas Weder [ 11/Sep/15 ] |
|
This has been around for such a long time... I'm not going to research this much more and rely instead on the fact that - if this errors indeed exists -, it will be raised again. |