[ABTEST-81] Store locking information to separate place when locking the node Created: 19/Sep/19  Updated: 08/Oct/19  Resolved: 03/Oct/19

Status: Closed
Project: A/B Testing
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Story Priority: Neutral
Reporter: Le Hai Thanh Assignee: Le Hai Thanh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3d 6.5h
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2019-09-24 at 9.20.56 AM.png     PNG File Screen Shot 2019-09-24 at 9.21.26 AM.png    
Issue Links:
Cloners
clones ABTEST-9 Lock the node when test is running Closed
Relates
relates to ABTEST-82 Research how to lock only the changed... 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)
Documentation update required:
Yes
Date of First Response:
Epic Link: Tests generation
Sprint: Add-Ons 21
Story Points: 5

 Description   

Currently, we are using JCR native lock/unlock function which might leads potential issues with lock session, lock token, ...

Please consider to store locking information to separate workspace so that we can fully control our locking component.

Have a content app to manage unlock independently? 

 


Generated at Sun Feb 11 22:52:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.