Cannot read property 'hasOriginal' of undefined
Asked by Luca Bellomi:

Cannot read property 'hasOriginal' of undefined  

TypeError: Cannot read property 'hasOriginal' of undefined  
at e.className (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-plan-scripts/com.atlassian.jpo:jpo-wr-page-plan-scripts.js?locale=en-UK:3:370765>)  
at Function.M.result (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/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-UK:86:20451>)  
at e._ensureElement (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/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-UK:96:33314>)  
at e.View (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/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-UK:96:31981>)  
at e.constructor (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/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-UK:502:17755>)  
at e.constructor (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/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-UK:502:22265>)  
at e.o \[as constructor\] (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-shared-scripts/com.atlassian.jpo:jpo-wr-page-common-shared-scripts.js?locale=en-UK:3:139834>)  
at e \[as constructor\] (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-shared-scripts/com.atlassian.jpo:jpo-wr-page-common-shared-scripts.js?locale=en-UK:3:20698>)  
at e.o \[as constructor\] (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-shared-scripts/com.atlassian.jpo:jpo-wr-page-common-shared-scripts.js?locale=en-UK:3:130942>)  
at e.n \[as constructor\] (<https://jira.dwnet.it/s/8eae2f31ecd8a8c5bdf98fe43a12372b-CDN/idzd1f/78001/0a8124ce5f26a3b87aa160e033132504/2.13.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-plan-scripts/com.atlassian.jpo:jpo-wr-page-plan-scripts.js?locale=en-UK:3:212116>)  

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

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36   
Local time: Mon Apr 23 2018 17:05:04 GMT+0200 (ora legale Europa occidentale)  

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

Plugin build: 2.13.0  

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

Jira Title: Different Web Project Management  
Jira Version: 7.8.1  
Agile Version: 7.8.0-DAILY20180223110622


Answers:
author: Earl McCutcheon
body: Hi Lucca,

We just tacked this issue down to Radio Button Custom Field types added to the plan, and created a bug report for it here:

- <https://jira.atlassian.com/browse/JPOSERVER-2365>

Regards,

Earl


author: Andy Heinzer
body: Hi Luca,

Can you tell us more about this error? What page in Jira were you looking at when this error is generated? Are other users effected? Does this appear in different browsers?

I can see this is making references to Portfolio specific resources, but it is still unclear to me what exactly is causing this problem.

This kind of error is something we have had similar cases (but with a different element than 'hasOriginal') over on Jira Software boards. For those cases, I would recommend taking a look at the KB: [JIRA Software: "Exception: Uncaught TypeError: Cannot read property 'fields' (or 'html') of undefined"](https://confluence.atlassian.com/jirakb/jira-software-exception-uncaught-typeerror-cannot-read-property-fields-or-html-of-undefined-779159021.html)

From that page, there is some more info on the causes and possible resolution:
>
> Cause {#toc-hId-1795123755}
> ---------------------------
>
> This can be caused by a third-party plugin
>
> OR
>
> a required field is not associated with any screen ("summary" for example is a recurrent situation).
>
> Resolution {#toc-hId--757033206}
> --------------------------------
>
> To troubleshoot the third-party plugin possibility:
>
> 1. Browse through Administration \> Add-ons \> Manage add-ons and then click on "Enable safe mode" (this will disable all plugins).
> 2. Check if the problem persists.
>
> To troubleshoot the field possibility:
>
> 1. Browse to fields (*Administration \> Issues \> Fields* and then click on the *Field configurations* menu tab on the left side of the screen);
> 2. Click on "Default Field Configuration".
> 3. Check all of the fields that are set as "Required".
> 4. Click on the "Screens" option for each Required field and check if these are associated with the "Default" screen.

I would try these steps to see if we can better understand what might cause this. In the case of using portfolio when seeing this, you might need to leave the Portfolio plugin and the Jira Software plugins enabled, to try to test this, or else the core functionality of those plugins might not be available (such as Jira Software boards like Kanban and Scrum).

comments: author: Luca Bellomi
body: I'm sorry but I've been far from my workstation in the last period.  
The problem was solved with an update of some external plug-ins on which some mandatory custom fields depend. At the same time an update of the Jira software version was also performed, but I do not know if this last action has affected the resolution of the problem.  

Thank you for your help!  
Luca


Tags: advanced-roadmaps

jira-software