[MGNLUI-3563] Notify initial user upon completing an asynchronous action Created: 09/Sep/15  Updated: 22/Oct/15  Resolved: 21/Oct/15

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Zdenek Skodik Assignee: Oanh Thai Hoang
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3d
Original Estimate: 0.5d

Issue Links:
duplicate
is duplicated by MGNLUI-3591 CommandActionTriggerListener sends pu... 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
Date of First Response:
Sprint: Saigon 15
Story Points: 8

 Description   

One can define an action as whether to notify the user who triggered it or not when the action completes. AbstractCommandAction#triggerComplete() sends the message to superuser only though. The action class already passes the current user name to the subsequent command, it'd would be nice if it can do so also for the UI message case then.



 Comments   
Comment by Oanh Thai Hoang [ 21/Oct/15 ]

Hi mgeljic, had

This is my understanding after investigating: 

- According to ticket, this is systematic issue and I have reproduced bug on version 5.3.9 (client report - SUPPORT-4858) but can't reproduce it in 5.3.4 (internal report - MGNLWORKFLOW-284) because the code has been refactored due to ticket MGNLUI-3510 (committed 5f9acc3d66c).

I found this issue happen on 5.2.x, 5.3.9 so there are my approaches and questions: 
- For version 5.3.12: Found the patch fix in MGNLUI-3591 (https://gist.github.com/mkgl/05e30173624e11e9ee34) for 5.3.12. So I don't need to fix this issue?
- For version 5.4.3: The code has been refactored due to ticket MGNLUI-3510 (committed 5f9acc3d66c) in version 5.4.1. So I don't need to fix in this version too?
- For version 5.2.x: Can’t find any fixing for this bug. Is it 5.2.x still in support life cycle? If yes. Could I apply the same patch fix of MGNLUI-3510?

Comment by Phu Ha [ 21/Oct/15 ]

I guess for 5.2.x you want to apply the same patch in MGNLUI-3591 instead, right!?

Comment by Mikaël Geljić [ 21/Oct/15 ]

Just restating here: I closed this ticket as duplicate of MGNLUI-3591 (and moved 3591 into the sprint instead).
5.2.x is still supported, but SUPPORT-4858 was reported on 5.3.9, therefore there is no need to fix it in 5.2.x.

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