Details
-
Bug
-
Resolution: Fixed
-
Low
-
8.0.2
-
None
-
Severity 3 - Minor
Description
Issue Summary
This is reproducible on Data Center: (yes)
While attempt using the automation for first time, the application will give an option to "get started" before actually loading the main automation page (AutomationProjectAdminAction), however when using this "Get started" option it fails in both scenarios described below.
Steps to Reproduce
- Move to “Administration”
- Manage apps
- Click “Automation for Jira”
- Click on “Get started”
- Select “Automate an existing project”
- Select any project in the drop-down then click on “Automate” button.
Expected Results
Shall redirect you to the main A4J page (AutomationProjectAdminAction).
Actual Results
Causing a hard-stop (cursor spinning with no action) and generating this error below on debug details at Chrome (F12):
batch.js:596 Uncaught (in promise) TypeError: Cannot convert undefined or null to object at Function.keys (<anonymous>) at i (batch.js:596:17102) at Object.sendUiEvent (batch.js:596:17456) at t.<anonymous> (batch.js:723:60271) at m (batch.js:707:96739) at Generator._invoke (batch.js:707:96492) at O.forEach.e.<computed> [as next] (batch.js:707:96919) at P (batch.js:723:58199) at a (batch.js:723:60465) at batch.js:723:60524
Workaround
Access the automation for Jira directly from the “Project Settings”.
Note
The same error happens if we select the option “Automate a sample Project” instead of “Automate an existing project”
Attachments
Issue Links
- relates to
-
JIRAAUTOSERVER-501 Automate a Sample Project fails with Unknown Error
- Closed
- is resolved by
-
A4J-3036 Loading...