[MGNLWORKFLOW-324] Preview page should show the version to be published not the current one Created: 26/Feb/16 Updated: 15/Apr/16 Resolved: 11/Mar/16 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.5.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Florian Fuchs | Assignee: | Ilgun Ilgun |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | quickwin, support, usability, ux | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25d | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| 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)
|
||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Sprint: | Basel 34 | ||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||
| Description |
|
In the detail view of a page publication task, there is a action "preview page". This action, however shows the current version of the page, not the version that is going to be published. You really expect to see the version of the page to be published. Steps to reproduce
-> You'll get to see the page as edited in step 3, not the changes published in step 1 (see attachment 4 SolutionPreviewPageAction does what it suppose to do, however, task object does not have a attribute called version in this context. I suggest to add the version attribute in PublicationTaskParameterResolver#setTaskContent, therefore PreviewPageAction can display the correct version of a given page. |
| Comments |
| Comment by Andreas Weder [ 07/Mar/16 ] |
|
Checked with ejervidalo: we're actually creating a new version of a page once you trigger a publication request. So what's really missing here is that we pass a long that version in the URL. The UI will actually do everything else automatically already:
I'm thus marking this as "quickwin" and raise its priority as it's both easy to fix but a usability issue at the same time. |