Skip to content

Console error (infinite skeleton spinner) on Jira Issues list.

Summary

I didn't see an issue for this yet, but while doing some exploratory testing on latest master, I found that Jira issues weren't loading (infinite skeleton spinner), but were being returned from the Api.

I'm still investigating (I'm unfamiliar with how Apollo is working with REST endpoints)

The syntax error is

[Vue warn]: Error in render: "TypeError: Cannot read properties of undefined (reading 'length')"

found in

---> <ExternalIssuesList> at ee/app/assets/javascripts/external_issues_list/components/external_issues_list_root.vue
       <Root>

and stems from the issues property in this component being set to undefined

NOTE

Navigating to closed issues (an empty array from the api) correctly resolves the page and does not set the issues property to undefined

Steps to reproduce

with an EE licensed GitLab instance:

  • create a new project and navigate to it
  • set up the Jira integration in settings > integrations > jira (Use a project key that has open issues)
  • navigate to the Jira issues for the project: Issues > Jira Issues

Example Project

This is reproducibl

What is the current bug behavior?

Syntax error and infinite spinner on Jira issue list page.

What is the expected correct behavior?

That the issues returned from the api display.

Relevant logs and/or screenshots

Screen_Shot_2021-12-03_at_4.21.44_PM

Screen_Shot_2021-12-03_at_4.21.36_PM

Output of checks

Results of GitLab environment info

This is happening from my local GDK instance connected to Jira running in a docker image from registry.gitlab.com/gitlab-org/gitlab-qa/jira-gitlab:8.8-project-and-issue

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes