I'm trying to connect my ADO to Jira but keep getting this message:
Hi @Nency Doshi ,
Hope you are doing well.
I am Dhiren, one of the Solutions Engineers working at Exalate.
Could you please let me know how you’re trying to integrate Azure DevOps with Jira?
I found something which might be helpful : https://support.atlassian.com/jira-cloud-administration/docs/integrate-azure-devops-with-jira/
In case you are open to try out other apps, I would recommend you to try Exalate.
It's a completely decentralized and fully bi-directional integration solution. You can sync Jira Issues with Azure WorkItems.
Exalate also provides you with a Groovy based scripting engine for limitless customizations!
Thanks, Dhiren
@Nency Doshi hi, in case you decide to switch the approach towards system integration - check out ZigiOps. It's a fully no-code integration platform that allows easy integration between different systems. ZigiOps can easily integrate Jira and Azure in no time.
Regards, Diana (ZigiOps team)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nency Doshi
The issue you're encountering occurs because your Azure DevOps (ADO) account and Jira account are on different tenants, which can cause authentication and authorization conflicts.
Here's how to resolve it:
Solution 1: Use a Personal Access Token (PAT) in ADO
If you're using an integration tool, it might require a Personal Access Token (PAT) for authentication.
1. Generate a PAT in ADO:
a. Go to your Azure DevOps portal.
b. Navigate to your User Profile → Personal Access Tokens.
c. Click New Token, set the desired scope (e.g., full read/write permissions for Work Items and Project), and generate the token.
d. Save the token securely; it will only be shown once.
2. Add the PAT in the Jira Integration Tool:
a. In Jira, go to the Integration Settings or the app/plugin you're using for integration.
b. Use the PAT for authentication with Azure DevOps instead of the standard login method.
Solution 2: Resolve Tenant Mismatch:
Your accounts being on different tenants means they may not share permissions or visibility. Fix this by linking the accounts through an intermediary approach:
A. Verify Azure DevOps Tenant
• Go to the Azure portal and check the tenant associated with your Azure DevOps account.
• Ensure that the organization you are trying to access exists in this tenant.
B. Verify Jira Tenant
• Ensure your Jira account is logged in to the tenant where your Jira instance resides.
C. Allow Cross-Tenant Access
• In Azure AD (Admin Rights Required):
o Ask your Azure AD administrator to add the Jira tenant domain as a guest or federated tenant.
o Ensure that the appropriate permissions are granted to access the ADO organization.
• In Jira Admin (if required):
o Ensure that your Jira instance allows external API access from Azure DevOps.
Solution 3: Use an Integration Platform
If cross-tenant management proves too complex, consider using an integration tool like OpsHub Integration Manager (OIM) - an enterprise-grade data integration platform which acts as a bridge between ADO and Jira.
1. Install and configure OIM.
2. Use credentials (PAT or OAuth) for ADO and Jira, ensuring separate authentication for each system.
3. Map the workflows, fields, and entities you want to sync.
Get started with OIM for free.
Thanks,
OpsHub team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your reply. I have discussed with my team and we have figured that Solution 1 would be the most ideal way. I've done Step 1- Got the PAT. But Step 2- I cant seem to see the integration settings anywhere in JIRA.
2. Add the PAT in the Jira Integration Tool:
a. In Jira, go to the Integration Settings or the app/plugin you're using for integration.
b. Use the PAT for authentication with Azure DevOps instead of the standard login method.
I am the admin for JIRA but don't see this Integration Settings. Could you please help?
Thanks,
Nency
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.