Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.6.0 - Cannot read property 0 of null. #41

Open
MichalKoscielniak opened this issue Dec 11, 2017 · 7 comments
Open

0.6.0 - Cannot read property 0 of null. #41

MichalKoscielniak opened this issue Dec 11, 2017 · 7 comments
Assignees

Comments

@MichalKoscielniak
Copy link

I have just installed the app ugraded to v2 ( was waiting for this for quite a while ), and unfortunately it does not work. When I click "New work item", it's creating an empty modal with no fields to populate. In the console i can see the error "Cannot read property 0 of null ( occuring in modal.js )". Similiar thing happens when i open "Link to work item" modal - it presents the same error as with new work item. Tested od both Chrome and Edge browsers.
zendesk_issue_1
zendesk_issue_2
zendesk_issue_3

@MichalKoscielniak
Copy link
Author

Found the answer on different thread. The issue is gone when i set additional credentials on PAT, as per below suggestion.
zendesk_issue_resolved

@BenGWeeks
Copy link

Agreed this was a bug as was seeing a similar issue with resolution above.

@dbr2hb
Copy link

dbr2hb commented Jan 3, 2018

Hi. I tried using the rights above, but still received the error. Only by granting all scopes access did it work. Maybe Microsoft is changing things?

@willsmythe
Copy link
Contributor

@trevorsg - can you take a look?

@sebastianzolg
Copy link

@dbr2hb @willsmythe Got the same issue. I solved it by giving the following scope rights on the PAT in VSTS:

  • Team dashboards (read)
  • Work items (read and write)
  • Work item search (read)

I think the documentation is wrong.

@pmosupport
Copy link

hi

I cannot seem to get the integration working..

Comments updated at either end do not flow through...

has anyone else had the issue bfore??

@ekozelek
Copy link

Leaving a note for anyone in the future who encounters this error - I was receiving it on the latest version using a PAT with work item read & write scopes. The fix for me was to give my PAT full access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants