[MAGNOLIA-2067] Updater: feedback message implies job is done before it actually is Created: 20/Feb/08  Updated: 20/Feb/08  Resolved: 20/Feb/08

Status: Closed
Project: Magnolia
Component/s: updatemechanism
Affects Version/s: 3.5.4
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Boris Kraft Assignee: Boris Kraft
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-1855 Update mechanism : better feedback to... 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)
Date of First Response:

 Description   

If you install a fresh 3.5.4, and add a module like PUR, point your browser to the update page, and start the update, it will list a message stating at some point "7 tasks have been executed, for a total of 7 tasks.".

It seems this message is shown when the 7th task is started, not completed. In fact the last task might take a while where nothing in the browser window changes, specifically, where the "start up Magnolia" button is not yet displayed.

When a user first experiences this, he does not know that such a button will follow, and does not know if he should wait or close the browser window or???

Since "7 tasks have been executed, for a total of 7 tasks." implies that all tasks have been finished, it should only display that message when this truly is the case.



 Comments   
Comment by Magnolia International [ 20/Feb/08 ]

dupe with http://jira.magnolia.info/browse/MAGNOLIA-1855

Comment by Boris Kraft [ 20/Feb/08 ]

i don't see it as a duplicate as such, but it probably is subsumed by MAGNOLIA-1855

Generated at Mon Feb 12 03:33:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.