Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,560,579
Community Members
 
Community Events
185
Community Groups

"api is not defined" when opening Program scope

Edited
Sergey Tcherednichenko
Sergey Tcherednichenko May 16, 2018

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

Answer
Watch
Like Be the first to like this
996 views

1 answer

1 accepted

1 vote
Answer accepted
Thomas
Thomas
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 16, 2018

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

View More Comments
Sergey Tcherednichenko
Sergey Tcherednichenko May 17, 2018

Hi @Thomas,

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

Best regards,

Sergey

Like
Sergey Tcherednichenko
Sergey Tcherednichenko May 18, 2018

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

Like • Denis Tsybulin likes this
Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced Roadmaps
TAGS
AUG Leaders

Atlassian Community Events

See all events