[MGNLSYNC-34] Last version is everytime synchronize even when it wasn't approved Created: 13/Nov/17 Updated: 29/Mar/22 Resolved: 14/Dec/17 |
|
| Status: | Closed |
| Project: | Magnolia Synchronization Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.1, 1.8.1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Milan Divilek | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| 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)
|
||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Sprint: | Kromeriz 122, Kromeriz 123, Kromeriz 124, Kromeriz 125, Kromeriz 126, Kromeriz 127 | ||||||||||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||||
| Description |
|
The above works as expected. But when I do the following: 1. create page X (v1) on author |
| Comments |
| Comment by Andrew Warinner [ 13/Nov/17 ] |
|
Another related use case: 1. Modify page X (version n) There are probably other cases around multiple versions and publications too. |
| Comment by Jan Haderka [ 14/Nov/17 ] |
|
This is the case also when running sync after the start of the workflow and before approval even w/o setting publication date. And was always the case. |
| Comment by Andrew Warinner [ 13/Dec/17 ] |
|
Customers expecting a fix |