Hi Atlassian support team,

      I am planning to integrate JIRA (paid version) with Crahlytics (Fabric), however, I am failing to do so.

      At my crahslytics account I am pushing link of my project created on JIRA along with correct credentials. I see error "Unexpected HTTP response from Jira - Message: Unauthorized, Status: 401". (Error screenshot is attached along with the issue ticket).

      The link and credentials are correct.
      What could be the possible cause of this issue ?

      Look forward to a quick response to this issue.

      Regards,
      Naveen Kothiyal

        1. Crashlytics Integration Issue.png
          289 kB
          SeeDoc TestTeam
        2. Screen Shot 2017-02-03 at 3.01.50 PM.png
          43 kB
          Juan Pablo Ghelfi

            [CLOUD-8519] Unable to integrate Crahlytics (Fabric) with JIRA

            Pavan Kumar added a comment - - edited

            Hi,

            I am able to Integrate...but I get http 400 error when I try to send Test can any one help me on this

            Pavan Kumar added a comment - - edited Hi, I am able to Integrate...but I get http 400 error when I try to send Test can any one help me on this

            Hi,

             

            As said by @Rodrigo above,

            Go to projects List, you'll see KEY column with respect to each project. Your project url is https://yoursite.atlassian.net/projects/KEY

            So something like https://amazon.atlassian.net/projects/AIOS  

            *KEY IS CASE SENSITIVE

             

            Apart from this, if your Jira password is managed by Google, then simply create a new API Token for fabric and use that as password. It will work.

            Yashika Katyal added a comment - Hi,   As said by @Rodrigo above, Go to projects List, you'll see KEY column with respect to each project. Your project url is https://yoursite.atlassian.net/projects/KEY So something like  https://amazon.atlassian.net/projects /AIOS   *KEY IS CASE SENSITIVE   Apart from this, if your Jira password is managed by Google, then simply create a new API Token for fabric and use that as password. It will work.

            Guruprasad padukone added a comment - - edited

            Still not able to integrate fabric with Jira, It's giving the error "Sorry we hit an unexpected error".

            Can someone help me out in this?

            Guruprasad padukone added a comment - - edited Still not able to integrate fabric with Jira, It's giving the error "Sorry we hit an unexpected error". Can someone help me out in this?

            Able to integrate on Jira using login credentials. But, getting a 400 error when on the "Send Test" Page. Any idea how to resolve that?

            Varun Jindal added a comment - Able to integrate on Jira using login credentials. But, getting a 400 error when on the "Send Test" Page. Any idea how to resolve that?

            Loc Le added a comment - - edited

            Updated 26/May/2018: Unfortunately, the following steps no longer resolve the issue.

            Original 18/Oct/2017:

            Hope this helps everyone that has been waiting for a solution. This is what worked for me...

            1. In JIRA, go to User Management.
            2. Select a user.
              • Note the username of the user.
            3. Click the Reset password button.
            4. The user will receive an email to reset their password.
            5. Click on the Change my password button in the email.
            6. Enter the desired password at the Atlassian ID website.
            7. Now go back to Fabric and enter the following:
              • JIRA project URL
              • JIRA username (from Step 2)
              • JIRA password (from Step 6)
            8. Click Verify.
               

            Previously, going directly to the Atlassian ID website and resetting my password did not work. When setting my password via a password reset request from JIRA, the integration works. Consequently, there might be a different password/token for JIRA vs Atlassian ID.

            Loc Le added a comment - - edited Updated 26/May/2018: Unfortunately, the following steps no longer resolve the issue. Original 18/Oct/2017: Hope this helps everyone that has been waiting for a solution. This is what worked for me... In JIRA, go to  User Management . Select a user. Note the username of the user. Click the  Reset password button. The user will receive an email to reset their password. Click on the  Change my password button in the email. Enter the desired password at the Atlassian ID website. Now go back to Fabric and enter the following: JIRA project URL JIRA username (from Step 2) JIRA password (from Step 6) Click Verify .   Previously, going directly to the Atlassian ID website and resetting my password did not work. When setting my password via a password reset request from JIRA, the integration works. Consequently, there might be a different password/token for JIRA vs Atlassian ID.

            Engineering added a comment - - edited

            I've done the same as @rsherman1 – it worked to setup and send one test.  However, subsequent tests fail with 400 status.

             

            I've had better success if I have a default assignee for new issues in the project in Jira

             

            However, adding an issue type (regardless if the issue type exists in the project or not) or a component type (regardless if the component exists in the project or not) will cause the verification to fail every time.

             

            All of the above is after about 20min of attempting to configure the integration.  Time will tell if it "sticks"

            Engineering added a comment - - edited I've done the same as @rsherman1 – it worked to setup and send one test.  However, subsequent tests fail with 400 status.   I've had better success if I have a default assignee for new issues in the project in Jira   However, adding an issue type (regardless if the issue type exists in the project or not) or a component type (regardless if the component exists in the project or not) will cause the verification to fail every time.   All of the above is after about 20min of attempting to configure the integration.  Time will tell if it "sticks"

            We set up a separate project as a clearing house for JIRA tickets...and created a "user" exclusively for JIRA with the required permissions. This worked for us...

            Robert Sherman added a comment - We set up a separate project as a clearing house for JIRA tickets...and created a "user" exclusively for JIRA with the required permissions. This worked for us...

            I managed to send Test but after few days, 401 appeared. Is there any way to make it work?

            Bart Wachowski added a comment - I managed to send Test but after few days, 401 appeared. Is there any way to make it work?

            I am able to Integrate...but I get http 400 error when I try to send Test

            Robert Sherman added a comment - I am able to Integrate...but I get http 400 error when I try to send Test

            I am ab le to Integrate...but I get http 400 error when I try to send Test

            Robert Sherman added a comment - I am ab le to Integrate...but I get http 400 error when I try to send Test

              Unassigned Unassigned
              f056570f47d2 SeeDoc TestTeam
              Affected customers:
              10 This affects my team
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: