Jira integration fails due username and password

I try to setup a JIRA integration for raygun, but it fails with username and password are wrong.

I created an application, navigated to "Application Settings" -> "Plugins" -> Jira and in the setup tab I entered the correct url, username and password and clicked on "save changes".

"Invalid JIRA credentials, please check the URL, Username or Password" is always the response. I use exactly the same credentials and url to log into jira, even from a plugin for intellij idea.

What can I do to drill down the problem? Are the special rights required to connect to jira?

Hi,

It looks like you have an invalid SSL certificate for that domain, I bypassed this to check for further errors and got a 404 from our initial call to the Jira API to check your credentials, this is of the form https://jira.rappid.io/rest/api/latest/myself. Are you able to check that this is not being hidden from external calls?

Thanks for digging into this issues. As I couldn't wait I also debugged and found out, that the raygun feature crawls url/rest/api/latest/myself.

The environment where we wanted to test this is actually jira.spreadomat.net. As I also saw the following payload for https://jira.spreadomat.net/rest/api/latest/myself

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <status> <status-code>404</status-code> <message>null for uri: https://jira.spreadomat.net/rest/api/latest/myself</message&gt; </status>

As I thought this is the problem with our installation, I tried a different jira installation with a newer jira version. Also there the same payload returned, but e.g. for jira.atlassian.com it worked. So basically I think it depends on the version.

The request is what for information do you need to retrieve from this resource and maybe it's possible to make this step optional.

All other features like creating new tickets or getting tickets via the api are working fine even with old jira installations. (5.x)

Would be nice to get this running as it seems related to many users even with different installations. Thanks Tony

Hi, we recently added this call in as many people were having issues entering invalid credentials or URLs. This allowed us to validate that everything was correct before continuing. I will have to have a look to see if there is another call we can use that is more widely supported with older versions of Jira.

Hi I have just altered the Jira integration to use a different method to validate credentials. Let me know if this fixes this for your older Jira instance. According to the Jira docs for the API this method should be on at least 4 or greater.

Hi Martin,

thanks for the quick fix. The setup now works and I can select a project. Sadly the creation of a ticket won't work, because of

Something went wrong! Here is what your Jira server returned: The issue type selected is invalid.

I think some required field isn't filled in. The issue type should be something generic from Jira and not a custom field.

Maybe you either could select the first option, or even better do the following. During the setup process, create a ticket and get the required fields with options. Display these fields and possible values in the setup process to let the user choose, which values should be default.

Thanks for your help Tony

Hi, we try to create a generic issue type of Task which has an id of 3. This generally seems to be available in most instances of Jira. Have you customised this issue type at all? We do plan to add support for picking issue types and filling in fields in the future