[MGNLUI-3343] CLONE - Asynchronous actions shows wrong requestor Created: 04/Feb/15  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.2.10
Fix Version/s: 5.2.x

Type: Bug Priority: Neutral
Reporter: Evzen Fochr Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: asynch-issue
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLUI-3330 Asynchronous actions shows wrong requ... Closed
dependency
depends upon MAGNOLIA-6060 CLONE - Add constant ATTRIBUTE_REQUES... Open
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   

To reproduce:
log in with eric, go to pages app, publish a subtree
log in with peter, go to pending tasks, requester is superuser and not eric

reason:
we use asynchronous actions for recursive publication, which IMO is not needed when using workflow.
see:
info.magnolia.module.workflow.commands.LaunchWorkflowCommand#getParameters
/modules/pages/apps/pages/subApps/browser/actions/activateRecursive@asynchronous



 Comments   
Comment by Evzen Fochr [ 04/Feb/15 ]

https://git.magnolia-cms.com/gitweb/?p=magnolia_ui.git;a=commit;h=f74b8323a1b7f86a396bd0b6b74fc47fb335faf8

Comment by Mikaël Geljić [ 04/Feb/15 ]
  • Unclear at the moment whether MGNLWORKFLOW-284 is supposed to affect Magnolia 5.2.x
    Moving out of 5.2.10 changelog, back to Open status.
Comment by Roman Kovařík [ 09/Mar/21 ]

efochr Is this still the case?

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