[MGNLHARDLK-48] As an editor I want the Hard Locking app (found in Discovery Release) has improvements Created: 25/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.12 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Phu Ha | Assignee: | Phu Ha |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | Code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: | |
| Account: | TeliaSonera (TELIA) |
| Epic Link: | Hard Locking Improvement |
| Sprint: | Telia - Sprint WishList |
| Description |
|
1/ Ability to share Locks among Instance(s). Example: The user A in 1st instance has locks on several nodes, these locks can be sent to 2nd instance (assumption: has the same users list, and nodes), then the user A on 2nd instance get the same locked nodes 2/ The application should follow the Magnolia standard module UX design, and behavior (reference to Advanced Versioning improvement #1 in ticket MGNLAVERS-48) |
| Comments |
| Comment by Viet Nguyen [ 04/Oct/18 ] |
|
Since we're not supporting multiple authors so this feature is irrelevant. Also in case customers having multiple instances, locking should not be shared between instances because we don't have the same content and indexes on multiple different Jackrabbit. |