"api is not defined" when opening Program scope

[Sergey Tcherednichenko]

Hi!

After updating to JIRA (from 7.8.0 to 7.8.1) and Portfolio (to 2.13.1) I have started getting an error when I open the "Scope" tab of the program (when I open the program's "Schedule" tab - it works fine). Tried in different browsers (Chrome, Firefox).

The error title is "api is not defined", and the description is the following:

---------------------

api is not defined

ReferenceError: api is not defined
at https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-program-scripts/com.atlassian.jpo:jpo-wr-page-program-scripts.js?locale=en-US:3:379538
at Function.M.map.M.collect (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:86:8826)
at n.map (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:96:18974)
at f.initialize (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-program-scripts/com.atlassian.jpo:jpo-wr-page-program-scripts.js?locale=en-US:3:379475)
at f.s.Controller (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:502:10318)
at f.e [as constructor] (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-shared-scripts/com.atlassian.jpo:jpo-wr-page-common-shared-scripts.js?locale=en-US:3:25092)
at f.i [as constructor] (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-shared-scripts/com.atlassian.jpo:jpo-wr-page-common-shared-scripts.js?locale=en-US:25:238902)
at new f (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-program-scripts/com.atlassian.jpo:jpo-wr-page-program-scripts.js?locale=en-US:3:378940)
at p.initialize (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-program-scripts/com.atlassian.jpo:jpo-wr-page-program-scripts.js?locale=en-US:3:343807)
at p.s.Controller (https://jira.my.domain/s/2372779d8500d41e975b5e13a439641b-CDN/-7v5d1/78001/4b07fe5146963ed6a907920bbffc4c86/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:502:10318)

===================
=== Client Info ===
===================

User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
Local time: Wed May 16 2018 15:47:48 GMT+0200 (CEST)

===================
=== Plugin Info ===
===================

Plugin build: 2.13.1

===================
=== System Info ===
===================

Jira Title: JIRA
Jira Version: 7.8.1
Agile Version: 7.8.0-DAILY20180223110622

---------------------

Is it a known issue of Portfolio 2.13.1? I could not find it in the bug-tracker, the most relevant issue I could find is this one: https://jira.atlassian.com/browse/JPOSERVER-438?jql=project%20%3D%20JPOSERVER%20AND%20text%20~%20%22api%20is%20not%20defined%22

Best regards,

Sergey

[Thomas · Accepted solution]

Hi @Sergey Tcherednichenko!

It doesn't seem to be a known issue indeed, could you reach out to support (https://support.atlassian.com/contact)? It will help us gather the needed information to solve this issue as I did not manage to reproduce it.

Cheers,

Thomas

[Sergey Tcherednichenko]

Hi @Thomas,

Thank you! I have raised a ticket and attached logs + screenshots.

Best regards,

Sergey

[Sergey Tcherednichenko]

Just in case if anyone else would face something similar - the problem was in the custom numeric field configured in the Program.

Here is the issue created for this bug: https://jira.atlassian.com/browse/JPOSERVER-2337