Join 34,000+ subscribers and receive articles from our
blog about software quality, testing, QA and security.

Unable to integrate with JIRA


#41

Yes, with my JIRA account in both and I got the same error 403


#42

Is there a way of getting some logs? to have more details on the error


#43

Hi Stéphanie,

Yes, there are logs and you would need to enable debug logging in this case. Are you on TestRail Server or TestRail Cloud? For TestRail Server, you can enable debug logging as follows:

http://docs.gurock.com/testrail-faq/system-debug

We can enable logging for TestRail Cloud instance if you send a quick email with your TestRail address to contact@gurock.com. In either case, we are happy to review the logs (just send them via email if you use TestRail Server).

Cheers,
Tobias


#45

Hi Tobias,
I hope you’re still around as you seemed to have helped plenty of users above with their JIRA/Testrail integration issues and am hoping you can help with mine.

I’m getting the following error message when I do a mouse-hover over a defect link:
“Plugin “Jira_REST” returned an error: Invalid HTTP code (404). Please verify the address of your JIRA installation in the configuration settings and that TestRail can reach your JIRA server.”

I don’t have TestRail admin access (yet), but am working with an admin locally. He has confirmed the address of our JIRA installation in the configuration settings and that TestRail can indeed reach our JIRA Server.

I’d be more than happy to supply debug logs (confirmed deploy_debug is set to ‘true’) in config.php, however, have not been able to locate these logs unless they are the daily logs found under /opt/testrail/logs/ directory.

I have more data points to share but would like to get your input first on best place to start given the above error.

Thank you!


Error received when viewing defect through Test Rail
#46

Update:
Just a heads-up, I was able to resolve the issue internally. It was a proxy/networking issue preventing authentication packets from getting through and thus the HTTP Error Code 404, which after troubleshooting turned into 401 and now after resolving the exact jira_REST URL, all is good.


#47

Hi there,

Thank you for the update. Glad to hear that you were able to get this resolved and thank you for posting your solution.


#48

error
Can anyone please help me about this…


#49

Have you tried any of the things mentioned in this thread and if so - what did you try what were the results? There are at least 2 things to look at for the 404 error in this thread.


#50

Hi,
Tried all the steps below expect the first one. Not sure where I can find this option.

  1. JIRA Admin/System - Accept remote API calls = on Not Checked

  2. JIRA username (not email) and password are entered correctly for the TestRail user. Checked

  3. Defect plugin set to Jira_REST. Checked

  4. The user variables are set to ‘jira_user’ and ‘jira_password’ Checked

  5. Fallback matches a JIRA user with correct access permissions (administrator just to be sure) ** Where can I find it? **

  6. The Plugin looks correct with Checked

[connection]
address=https://xxxxx.atlassian.net/
user=%jira_user%
password=%jira_password%

Reference URL is not working for me. I have entered the reference url as “https://qmacbis.atlassian.net/browse/%id%” but still I see an issue when i click on the Reference url link in Test cases.
Following is the error message i received -

Plugin “Jira_REST” returned an error: Invalid HTTP code (404). Please verify the address of your JIRA installation in the configuration settings and that TestRail can reach your JIRA server.