View #129 on GitHub to know more details
I am unable to integrate to jira assistant. It always shows me network server error. PLease check "This is not a valid Jira server url or the server does not respond." Where as we are using the same jira url
I think the URL is meant to be:
Try that and it should work
[image: image.png]
getting the above error on trying with the suggested url.
On Thu, Feb 20, 2020 at 3:12 PM Szabotic notifications@github.com wrote:
I think the URL is meant to be:
Try that and it should work
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/shridhar-tl/jira-assistant/issues/129?email_source=notifications&email_token=AORLTHWOSYCGNEY4SWUPDD3RDZGANA5CNFSM4KYK5KC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMMUMRA#issuecomment-588858948, or unsubscribe https://github.com/notifications/unsubscribe-auth/AORLTHSOGRMRHYHKCJAB5OLRDZGANANCNFSM4KYK5KCQ .
GEtting the above error
I am unable to integrate to jira assistant. It always shows me network server error. PLease check "This is not a valid Jira server url or the server does not respond." Where as we are using the same jira url
Same issue
It works on Firefox, Jira Assistant 0.96
Please try using Firefox version for now. v0.96 would be available in chrome in next 4-5 days depending on the review process in chrome web store. At the mean time try to open console and check if you see any errors related to CORS. If you see it then their is no immediate solution as this is due to an update in chrome browser and I am yet to figure out a way to solve it.
New Version on Firefox seems to work.. little slow but works.. Thanks a lot Shridhar!!
Hi @vinaychavadi - I know it it bit slow. Due to the security updates given by Chrome currently (which will be published for Firefox also later), I will have to change some approach to have the tool overcome those restrictions which made requests to Jira bit slower. I will try and find a better option once the tool becomes stable once again.
Thanks Shridhar. This tool is of great help for all of us who log our work in Jira in our organization. Thanks for your help. We look forward for the new version of the tool. For now we are happy that this works :)
Hi @vinaychavadi - I know it it bit slow. Due to the security updates given by Chrome currently (which will be published for Firefox also later), I will have to change some approach to have the tool overcome those restrictions which made requests to Jira bit slower. I will try and find a better option once the tool becomes stable once again.
I am still getting the same error as mentioned in the thread in both Chrome and Firefox.
The new 0.96 version is available now on Chrome and seems to be working fine.
When selecting a Date on "Worklog Report" i still get the "One or more Actions Failed". All the other reports seem to work fine.
Version: 0.96 Browser: Firefox and Chrome
_uniqueId: (...) error: {errorMessages: Array(1), errors: {…}} response: "{"errorMessages":["Error in the JQL Query: The character '%' is a reserved JQL character. You must enclose it in a string or use the escape '\u0025' instead. (line 1, character 4)"],"errors":{}}" status: 400 ref: {readyState: 4, getResponseHeader: ƒ, getAllResponseHeaders: ƒ, setRequestHeader: ƒ, overrideMimeType: ƒ, …} proto: Object
{"errorMessages":["Error in the JQL Query: The character '%' is a reserved JQL character. You must enclose it in a string or use the escape '\u0025' instead. (line 1, character 4)"],"errors":{}}
Please try using Firefox version for now. v0.96 would be available in chrome in next 4-5 days depending on the review process in chrome web store. At the mean time try to open console and check if you see any errors related to CORS. If you see it then their is no immediate solution as this is due to an update in chrome browser and I am yet to figure out a way to solve it.
@shridhar-tl Getting the following error when installing JiraAssist_Latest.xpi in Firefox 73.0.1
I have got it working by installing Firefox Developer edition and diabled xpinstall.signatures.required
, xpinstall.whitelist.required
and extensions.langpacks.signatures.required
and then installing from the XPI file.
Duplicate of #126 . Hence closing this issue. You can track for any updates through #126. Also v0.97 is already available in Firefox and should fix all the issues mentioned. For chrome it would take some time for the review to be completed by Google and hence expected date for the update to be available for chrome users is 3rd of March 2020.