Skip to main content
A
ayushb2032
February 6, 2025
Question

Assistance Needed for Appian-JIRA Integration

  • February 6, 2025
  • 1 reply
  • 0 views

Hi Everyone,

I need to implement functionality to read, write, and update specific JIRA tickets through an integration between Appian and JIRA. For this, I'm referring to the JIRA API documentation:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get

 

To authenticate, I plan to use OAuth 2.0 (Authorization Code Grant) as outlined in the documentation here:

https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/

 

I have already created the necessary app in the Atlassian Developer Console for OAuth 2.0, and I successfully set up the connected system in Appian. However, I'm encountering an error while trying to create the integration system.

Could anyone please assist me in resolving this issue and help me complete the Appian-JIRA integration?

 

Thank you!

    1 reply

    N
    nassera300561
    February 18, 2025

    Seems to be an authetication issue, can you reauthorize the OAuth 2.0 Connected System in Appian? Try:
    Admin Console > Connected Systems
    Find your JIRA OAuth 2.0 connected system
    Click Authorize to generate a new access token

    Ensure that your Client ID, Client Secret, and Authorization URLs match what’s provided in the Atlassian Developer Console and the Redirect URI in Atlassian matches the one in Appian. 

    Maybe try updating integration's authorization header:
    e.g.

    a!httpRequest(
  method: "GET",
  url: "https://your-jira-instance.atlassian.net/rest/api/3/issue/{issueIdOrKey}",
  headers: {
    a!httpHeader(name: "Authorization", value: "Bearer " & ri!accessToken)
  }
)

    Sometimes (may not be the case but might be worth the shot) jira's OAuth tokens have a limited lifespan. If expired, refresh the token using the refresh token flow. 

    Please reach out if you require any further assistance, this error just seems to be a bearer authentication issue so maybe one of these options can make sure it's fine. 

    Terms & ConditionsAccessibility statement