[ABTEST-92] Automatically unlock or lock nodes based on the test state Created: 03/Oct/19 Updated: 13/Dec/19 Resolved: 11/Dec/19 |
|
| Status: | Closed |
| Project: | A/B Testing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Andrei Ichimescu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25d | ||
| Original Estimate: | Not Specified | ||
| 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: | Testing scenarios & goals |
| Sprint: | Add-Ons 26 |
| Story Points: | 3 |
| Description |
|
AC
|
| Comments |
| Comment by Andrei Ichimescu [ 10/Dec/19 ] |
|
System startup handles in the correct way, as the lock is persistent in jcr, therefore page nodes will remain locked even after a restart |