Details
High Description
Summary
When add a custom field in JIRA and then associate it to the program, it throws the following stack traces:
api is not defined ReferenceError: api is not defined ...
Environment
- JIRA Portfolio 2.13.1
Steps to Reproduce
- Create a custom field in JIRA Eg: number field or text field
- Go to your Program in Portfolio > Configure > Custom fields > Add custom field
- Select the custom field you had just created to the Program
Expected Results
It should work just fine
Actual Results
The following error is shown:
api is not defined ReferenceError: api is not defined at http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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 (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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 (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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 (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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 (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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] (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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] (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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 (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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 (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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 (http://10.60.3.208:8760/jira/s/72a27af5c96bcd379454aa5cb5747a70-CDN/-mp2ypd/76001/b6b48b2829824b869586ac216d119363/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 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Local time: Fri May 18 2018 16:55:17 GMT+0800 (+08) =================== === Plugin Info === =================== Plugin build: 2.13.1 =================== === System Info === =================== Jira Title: Your Company JIRA Jira Version: 7.6.0 Agile Version: 7.6.0-DAILY20171103151351
Notes
It doesn't affect the functionality of the Program however it is annoying because everytime you refresh the Program page, it will throw the same error message.
Workaround 1
Temporary remove any custom fields from the Program
- Navigate to the plan and select configure >> Custom Fields
- Select Remove from plan next to each field added to the plan settings
Workaround 2
Another workaround is to downgrade to Portfolio version that did not affect by this Bug. (Tested downgrade to v2.11)
- Uninstall all 3 plugin packages related to Jira Portfolio from Manage Add-ons.
- Portfolio for Jira
- Portfolio Live Plans
- Portfolio Team Management
- Stop Jira.
- Remove the v2.13.1 jar file from <jira-home>/plugins/installed-plugins.
- Start Jira.
- Re-install Portfolio v2.11 OBR. (This can be Download here)
