[MGNLCAT-134] Reconfigure availability of de/activation and other actions Created: 30/May/14  Updated: 25/Jul/14  Resolved: 10/Jul/14

Status: Closed
Project: Magnolia Categorization Module
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.2.3, 2.3.1

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Peili Liang
Resolution: Fixed Votes: 0
Labels: quickwin, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-2945 Action availability with writePermiss... 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)
Date of First Response:
Epic Link: publishActionsAvailability

 Description   

Since any de/activation request actually attempts to write to involved node/s, to update its metadata, the actions should be implicitly allowed only for users having write permissions to them. Since MGNLUI-2510 it's trivial to restore this former 4.5 like behaviour. Thes to any actions resulting in write events.



 Comments   
Comment by Peili Liang [ 17/Jun/14 ]

I try to fix the issue in 2.1.x, but it seems that 2.1.x depends on magnolia 5.1(main and ui). if it depends on magnolia 5.2, then I guess the fix version should be 2.2.x, but I can not find the 2.2.x
finally I reassign the ticket to unassigned.

Generated at Mon Feb 12 04:43:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.