[MGNLHARDLK-44] As an editor I want my locked nodes put in 'excluded list' when someone try to lock its parent node Created: 12/May/15  Updated: 04/Oct/18  Resolved: 04/Oct/18

Status: Closed
Project: Project - Telia - Hard Locking (closed)
Component/s: None
Affects Version/s: 0.1
Fix Version/s: 0.3x

Type: Story Priority: Neutral
Reporter: Phu Ha Assignee: Phu Ha
Resolution: Fixed Votes: 0
Labels: Code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLHARDLK-2 As an editor I want to hard lock my c... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Account: TeliaSonera (TELIA)
Epic Link: Hard Locking
Sprint: Telia - Sprint WishList

 Description   

In the Assets App

If the node gets locked by user A, meaning, by design, the child nodes should be locked by user A also

Expected result: The parent node cannot be locked by someone else so that it overwrites the lock in its child nodes by user A
Actual result: The user B or someone else is still able to lock the parent node. Then the user A loses locks on its node



 Comments   
Comment by Phu Ha [ 13/May/15 ]

This is by nature of design, we tend not to implement the 'excluded list'. So skip it for now, this can be 'Would Have' feature, meaning not any commitment on the Scope of Works, and can be planned later

Comment by Viet Nguyen [ 04/Oct/18 ]

If a user lock a parent node with the option of also locking its children.
Then that user must have permission to unlock all of his children nodes and no 'excluded list' should be implemented to decrease system complication.
Let's close this issue here to clean up our backlog.

Generated at Mon Feb 12 10:32:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.