Issue Summary

Trying to transition an issue doesn't work/gets stuck on first-page load if they use a screen

Steps to Reproduce

1. Add a screen to any transition in your workflow.
2. Get the issue to the point where you would normally make the transition.
3. Copy the issue URL
4. Close the web browser (wait a couple of seconds to ensure the underlying process is also closed).
5. Open the web browser, paste the issue URL, and access the issue.
6. Attempt to transition the issue.

Expected Results

The screen linked to the transition appears

Actual Results

On first page load, the screen will be blocked as usual when a screen is about to appear, but the screen will not be displayed.

See video: Transition screen getting stuck on first page load.mp4

Notes:

• If the user presses Escape, the page block will be undone, and if the transition is attempted once more, the same problem will occur.
• The scenario affects specially users who access their Jira tickets directly from their email notifications, as they may be working on something else, our of a web browser, and only open it to access Jira.
• Errors can be seen in the dev tools console:

  ajax[64626892] error : {
  successful  : false,
  status      : 200,
  statusText  : parsererror,
  hasData     : true,
  readyState  : 4,
  requestId   : 64626892,
  aborted     : undefined,
  }
  VM184:1 Uncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.
      at eval (eval at <anonymous> (batch.js:27:11120), <anonymous>:1:15)
      at eval (<anonymous>)
      at batch.js:27:11120
      at Function.globalEval (batch.js:27:11131)
      at HTMLScriptElement.<anonymous> (batch.js:34:23080)
      at Function.each (batch.js:27:11516)
      at init.domManip (batch.js:34:22956)
      at init.append (batch.js:34:20211)
      at d (batch.js?locale=en-US:1370:2210)
      at j.buildDialogErrorContent (batch.js?locale=en-US:1370:3519)
      at $content.i.complete (batch.js?locale=en-US:2942:5127)
      at Object.u [as complete] (batch.js?locale=en-US:1370:892)
      at d (batch.js:27:14462)
      at Object.fireWith (batch.js:27:15221)
      at r (batch.js:35:988)
      at XMLHttpRequest.r (batch.js:35:6694)

Workaround

• Refresh the page. After that, all transitions will display their screens as expected for as long as the web browser is not completely closed.
• Open a new tab and open the same issue. After that, all transitions will display their screens as expected.