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

Cannot read property 'Deferred' of undefined

Scott Maier May 16, 2018

I installed the Portfolio add-on. When I try to create a plan for the first time, I get to step 4 of 5 and when I click next I get the following error and cannot proceed:

 

Cannot read property 'Deferred' of undefined

TypeError: Cannot read property 'Deferred' of undefined
at Object.createPreDeferred (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/2.13.1/_/download/batch/com.atlassian.jpo:jpo-wr-page-create-plan-scripts/com.atlassian.jpo:jpo-wr-page-create-plan-scripts.js?locale=en-US:3:263273)
at i.createTransitionDeferred (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:278928)
at i.onNextRequested (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:277419)
at i.next (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:276880)
at y (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:21985)
at v (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:21777)
at f (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:19705)
at n.c.trigger (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:21670)
at Object._triggerMethod (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:7772)
at n.triggerMethod (http://jira.spxflow.com/s/1ac688abaca3c691ad25dfde107ada20-CDN/en_US-6zsavf/70107/f671a5ed10a8a1fbb785c8d1a0052a57/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:21147)

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

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.170 Safari/537.36
Local time: Wed May 16 2018 11:45:55 GMT-0400 (Eastern Daylight Time)

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

Plugin build: 2.13.1

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

Jira Title: SPX Flow, Inc.
Jira Version: 7.0.0
Agile Version: 7.0.11

3 answers

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 25, 2018

Hi everyone,

I took a look through this error, and found a few other reported cases of this error on our support tracker.  From what I have found so far, it appears this error can happen when installing these more recent versions of Portfolio (such as 2.13.x) when your underlying version of Jira is running much older (and end of life versions) such as Jira 6.3, 6.4, and 7.0.   I created a bug for this behavior in Portfolio over in https://jira.atlassian.com/browse/JPOSERVER-2342  Please watch and vote on this issue.  I would recommend watching this bug for updates on this problem.

In the meantime, I found a few different possible work-arounds:

So one possible solution here is to upgrade Jira Core and Jira Software to a more recent version, such as 7.3 or higher, and then install this current version of Portfolio.

Alternatively, if upgrading Jira core/jira software is not preferred for some reason, I instead would suggest to try to install an older version of Portfolio that was released on or about the same time as your current version of Jira Software/Jira Agile.   You can find a complete list of the versions of Portfolio and their release dates on https://marketplace.atlassian.com/apps/1212136/portfolio-for-jira/version-history
Also you can find the release dates for Jira Software from the release notes: https://confluence.atlassian.com/jirasoftware/jira-software-release-notes-776821069.html
In my case I was able to use a Jira 6.4.13 version along side an older version of Portfolio such as 2.2.6 and this bug did not present itself.

I hope this helps.

Andy

Steve Schiff June 4, 2018

Same problem here - running 7.1.X of Jira and the latest portfolio. 

0 votes
Thomas
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 21, 2018

Hi @Scott Maier / @Loren Reich,

 

I'd strongly suggest contacting support (https://support.atlassian.com/contact/) for this issue, as a support issue will be a better place to share the required information to understand what is happening here.

 

Cheers,

Thomas

Pete75 May 23, 2018

Same problem here - was there any solution??

0 votes
Loren Reich May 21, 2018

I have the same problem.

Did you find a solution?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events