Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira cloud integration with monday.com is failing

Mohajit Acharya
Contributor
April 1, 2022

I am getting an error while trying to integrate Jira with monday.com. Have tried Chrome (even in incognito mode) and MS Edge but no luck. Find attached the screenshot of the error message. Jira Global Admin's credential is used for this integration using the correct Jira API token and Jira Subdomain.

Following the instructions as given in the below link:

https://support.monday.com/hc/en-us/articles/360002296399-Jira-Cloud-Integration 

Any help would be greatly appreciated!

SS1.png

2 answers

2 accepted

0 votes
Answer accepted
Mohajit Acharya
Contributor
April 4, 2022
The issue is resolved. The subdomain name has to be entered as a simple text and not as a full URL with subdomain dot atlassian dot net. 
Have provided this feedback to monday dot com support as the help text against the "Subdomain" field says the user has to enter the complete URL.
0 votes
Answer accepted
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 1, 2022

Hi @Mohajit Acharya ,

Bummer that the integration is not working! I would recommend reaching out to Monday.com's support as they operate that integration on their site (we don't manage it here at Atlassian). I imagine they're storing the token locally, so there shouldn't be a problem using various browsers to submit the details on that screen.

As an aside though, I do see you need to relaunch Chrome to update :)

If you wanted to, you could test those credentials by calling the myself API endpoint:

yoursite.atlassian.net/rest/api/3/myself

When making a call to that endpoint with Basic Auth in postman (or tool of choice like curl), the "username" is the email address of the account, the "password" is the API token, and the return should show information about that user. It will return a 401 if there was some problem with the API token.

Cheers,
Daniel

Mohajit Acharya
Contributor
April 2, 2022

Hello @Daniel Eads , thanks a lot for your response. I have updated my Chrome and relaunched and tried again but no luck. As per your advice, I tried sending a GET message using https://jkdmarketing.atlassian.net/rest/api/3/myself API endpoint and got the below response. Could you please let me know the possible issue here from the error message below? Does it mean that the user name (email address) used for doing this integration does not have the required permission (not a Jira Global admin)?

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<status>
<status-code>401</status-code>
<message>Client must be authenticated to access this resource.</message>
</status>

Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 3, 2022

The /myself endpoint there doesn't require admin permission - it should return results for any user if the credentials are valid.

Getting a 401 here could mean a couple things:

1. The GET request wasn't configured with the email address / API token when it was sent

2. (more likely, based on Monday.com also having an error) - the API token you have doesn't pair with the email address for the username.

I've reviewed the instructions Monday.com provides for generating an API token and they should work - just need to be signed into the account you're going to use for authentication. In the case of this integration, it should be an account that has Jira Administrator permission in Jira. The instructions we provide for creating an API token in Atlassian Cloud are a bit shorter if you want to follow those instead.

I would recommend logging back into the account with Jira Administrator permission and generating a new token. It looks like the one you've got is either from a different account, revoked, or was missing some characters when it was copied.

Mohajit Acharya
Contributor
April 3, 2022

Many thanks, Daniel for your detailed analysis. I have tried again by creating a new token but no luck. But this time I have taken the screenshot of the console log which I am pasting below. I have written to monday.com support as well.

SS1.png

Suggest an answer

Log in or Sign up to answer