Open mirgee opened 8 years ago
Hmm, you might be hitting a bug in the underlying JIRA library itself in that it doesn't handle paths on the URL correctly right now. I think there is a patch for the library, but I haven't tried it myself yet.
Just my 2 cent insight. I had the same error. I searched for the string "Invalid issue number" in the jira.js library. Before the dorequest method, I added the callback(options.uri);
line to check which url was used to do the request.
Based on your current configuration, the url may be https://jira.concur.com:443/rest/api/2/issue/MOB-27579 but you probably want to target https://jira.concur.com:443/jira/rest/api/2/issue/MOB-27579 (try it in a browser).
To do so, I used the port as a workaround:
port: '443/jira
and voila, it worked.
Hope it helps.
Hi, I get the bot to correctly find the project name, and login to the Jira server, however, it returns Invalid issue number message, altough the issue number is correct. I believe everything in the config file is setup properly, so I think the culprit is in the API call, maybe there is a bug in the way the plugin formats the API call. I would like to ask - how does the plugin format the API call? E.g. the string "MOB-27579" is mentioned, the message "MOB-27579 - Invalid issue number." is returned. Shouldn't the number be just "27579"? Thank you!
Here is my config file, can you please take a look? Does it seem OK? Thank you!