Actually, thinking about this issue a bit more, I think we should ask for confirmation from the user about what should be done, using buttons. By default the action should not start, maybe, and a button should allow the user to say what they want to do, if they want to keep waiting or cancel the job or something, to force the user to pay attention to the message and make sure that they understood its consequences.
Anca Luca on 26/Mar/26 14:23
Actually, thinking about this issue a bit more, I think we should ask for confirmation from the user about what should be done, using buttons. By default the action should not start, maybe, and a button should allow the user to say what they want to do, if they want to keep waiting or cancel the job or something, to force the user to pay attention to the message and make sure that they understood its consequences.
I mean, the message itself is pretty clear, to me, but it's not clear whether the users actually read it and understand it. Also, for users that haven't done a move in a long time or never, it's not clear for them that that is not necessarily the "normal" UI for a job that was executed / is executing (they don't know that they should be seeing a progress bar or a green message), so they may believe that it's done, close the window, then navigate in the wiki and see that their content is still not moved and then start another move.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
