[MGNLUI-3353] Do not send both UI-notifiaction and pulse message after asynchron action execution Created: 18/Feb/15  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.3.7
Fix Version/s: 5.3.x

Type: Improvement Priority: Neutral
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: asynch-issue, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-3352 Asynchron action execution should not... 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)

 Description   

At the end of an asynchron action execution, both UI-notifiaction and pulse message are sent.
When it is really asynchron, pulse message is sufficient.

The issue might be related with MGNLUI-3352.


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