Skip to content
This repository was archived by the owner on Nov 4, 2022. It is now read-only.

Error running gh ji #78

Open
jwu910 opened this issue Dec 17, 2019 · 5 comments
Open

Error running gh ji #78

jwu910 opened this issue Dec 17, 2019 · 5 comments

Comments

@jwu910
Copy link

jwu910 commented Dec 17, 2019

TypeError: Cannot read property 'user' of undefined
    at Jira.normalizeOptions (/home/joshua/.nvm/versions/node/v10.16.0/lib/node_modules/gh-jira/bin/jira.js:775:59)
    at Jira.run (/home/joshua/.nvm/versions/node/v10.16.0/lib/node_modules/gh-jira/bin/jira.js:180:14)
    at getCommand.fork (/home/joshua/.nvm/versions/node/v10.16.0/lib/node_modules/gh/lib/cmd.js:175:39)

@protoEvangelion is gh-jira not compatible with recent releases of node-gh?

I just updated gh to 2.8.3 but gh-jira is still at 1.0.7.

I haven't been able to get gh-jira to work with node-gh in a while. Has this been on the radar? I vaguely remember the security changes that were made to the JIRA server we use caused issues in the past, but wondering that was a one time fluke or if it's a reproducible problem.

Thanks!

@protoEvangelion
Copy link
Member

Hey @jwu910 👋 I haven't been maintaining gh-jira, for a while, however I did test it successfully for v2 of gh with a manual workaround.

I'm pretty sure your issues have something to do with Jira's required oauth handshake. In the past we could just send over basic auth (user & pass) but they don't allow that method of auth any more.

Let me know if you have any ideas of how to approach this!

@jwu910
Copy link
Author

jwu910 commented Dec 23, 2019

I haven't worked with this type of functionality yet, and am interested, but at this moment--no ideas, sorry.

I remember this came up when we made changes to our JIRA auth, so maybe it's still a problem. Not that big a issue. You can close this or maybe consider a request for comments/help wanted

@protoEvangelion
Copy link
Member

That sounds about right. Thanks for raising the issue! I'll leave it open.

@protoEvangelion
Copy link
Member

Side note, I'm actually thinking of deprecating this plugin along with the concept of plugins. The same thing can be accomplished through hooks (ie state sharing). Any thoughts?

@jwu910
Copy link
Author

jwu910 commented Mar 6, 2020

I dont think its a critical package, it's a great workflow benefit, but it was really only saving a couple clicks. I think post-PR scripts with gh can help partially automate the use case I wanted to solve anyways.

Thanks for the consideration! Hope all is well!

Feel free to close

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

No branches or pull requests

2 participants