Easy Question: Looking to Better Understand Workfront Fusion Module - JIRA CLOUD CUSOTM API Call | Community
Skip to main content
D
D____D
Level 4
August 16, 2024
Solved

Easy Question: Looking to Better Understand Workfront Fusion Module - JIRA CLOUD CUSOTM API Call

  • August 16, 2024
  • 1 reply
  • 819 views

Hello, 

I'm having a hard time understanding the JIRA API Module for Custom API Calls. When configuring the "connection" for this Module, one of the things it asks you is the "Service URL"  and I'm really confused what this URL is since it calls it "Instance URL" ???? Is the instance and service URL the same thing? 

 

It's described as the jira instance URL ... what is that? 

 

Is it your - https // < jira server instance>.atlassian.net /  ... address

Is it your - https // <some other path that I don't know > / ... address found within JIRA Admin Console

Is it your - https // <jira server instane.atlassian.net / rest / api / <version #>  ... address

or is it just something else .. 

I've checked the documentation for this via the "?" on the module but that leaves a bit to be desired for someone configuring it for the first time. Any thoughts on which URL this is. I've tried a few and none of them work.  



Thank you! 🙂 


This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by D____D

I had to setup a call with Adobe to actually figure this out with them and to my surprise, we both had to work through this one (meaning that even some of the folks at Adobe had to scratch their head on this). Here are the instructions more plainly written for anyone to understand to leverage the JIRA Custom API Module correctly - 

  • Log into your JIRA instance and navigate to your API Admin page (this link as of 08/2024) (https://id.atlassian.com/manage-profile/security/api-tokens)
  • Create an API token 
  • Keep the user name created for that token handy and the token itself 
  • Log into Fusion, create a scenario, add a JIRA module, and add a connection using the JIRA Custom API
  • In the Service URL portion of the New Connection, only include https://<yourdomain.atlassian.net>
  • Enter the JIRA User Name (could be email) and API Token
  • If that works, it will go through without issue, or bark at you 😄 
  • Back on your Custom API Module, this was the gotcha  
    • Unlike things like post man, or doing a dirty api call over a browser, you have to only enter queries like this where the URL field only has the object type you are trying to query (not the full path as it suggests)
    • In this case, just "project" - nothing else

So you could replace that with Issues, Tasks, Comments, etc (reference for the correct name of objects in JIRA).  Also note that JIRA is really case sensitive, so those things matter even when coming from Fusion 

 

Best of luck.

Very grateful to the folks at Adobe who helped clear this up. Figured I'd share here in case anyone runs into this or gets stuck. 


1 reply

D
D____DAuthorAccepted solution
Level 4
August 30, 2024

I had to setup a call with Adobe to actually figure this out with them and to my surprise, we both had to work through this one (meaning that even some of the folks at Adobe had to scratch their head on this). Here are the instructions more plainly written for anyone to understand to leverage the JIRA Custom API Module correctly - 

  • Log into your JIRA instance and navigate to your API Admin page (this link as of 08/2024) (https://id.atlassian.com/manage-profile/security/api-tokens)
  • Create an API token 
  • Keep the user name created for that token handy and the token itself 
  • Log into Fusion, create a scenario, add a JIRA module, and add a connection using the JIRA Custom API
  • In the Service URL portion of the New Connection, only include https://<yourdomain.atlassian.net>
  • Enter the JIRA User Name (could be email) and API Token
  • If that works, it will go through without issue, or bark at you 😄 
  • Back on your Custom API Module, this was the gotcha  
    • Unlike things like post man, or doing a dirty api call over a browser, you have to only enter queries like this where the URL field only has the object type you are trying to query (not the full path as it suggests)
    • In this case, just "project" - nothing else

So you could replace that with Issues, Tasks, Comments, etc (reference for the correct name of objects in JIRA).  Also note that JIRA is really case sensitive, so those things matter even when coming from Fusion 

 

Best of luck.

Very grateful to the folks at Adobe who helped clear this up. Figured I'd share here in case anyone runs into this or gets stuck. 


Terms & ConditionsAccessibility statement

Loading footer...