Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


"api is not defined" when opening Program scope



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 (
at (
at f.initialize (
at f.s.Controller (
at f.e [as constructor] (
at f.i [as constructor] (
at new f (
at p.initialize (
at p.s.Controller (

=== 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:


Best regards,


1 answer

1 accepted

1 vote
Answer accepted
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 ( It will help us gather the needed information to solve this issue as I did not manage to reproduce it.




Hi @Thomas,

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

Best regards,


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:

Like Denis Tsybulin likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events