• Documentation
  • Workato Blog
  • Product Blog
  • Return to Workato
  • Login
  • Automation Institute
  • Documentation
  • Community Forums
New Topic
Discussions Recipe Building Recipe Error Troubleshooting
J

JIRA Integration

started a topic about 6 years ago
Answered

Not able to see a custom field in the recipe from JIRA

Just giving the reference of recipe, don't know by the time if I change it


https://www.workato.com/recipes/487672-latest-sfdc-case-gets-updated-on-update-of-jira-issue#recipe


image



Here is the screen shot of the field from Jira

image




Best Answer
C
CJ Wee said about 6 years ago

Hi Mark,


While the Epic Link data pill is currently not accessible, this issue can be worked around using our HTTP connector. I have successfully implemented this for you while working with Kalpesh.


To others who are interested in this solution, you can follow the steps below.


1) Create a HTTP connection to JIRA. Give the connection a name, set authentication to Basic, and fill up the auth user and password which are your JIRA user login and password credentials. Do note that this needs to be the credentials of a JIRA System Admin


image


2) In the recipe where you need the JIRA epic link, create a new action, with application set to HTTP. The action will default to "Make REST request".

Give the request a name (up to you to decide), and add the Request URL as shown below. The highlighted portions in the URL should be changed to your JIRA hostname (url) and JIRA issue key (or ID) respectively. For the JIRA issue key (or ID), you can map a data pill into that portion of the URL instead of hard coding the value.


image


3) Next, leave the Request body empty, Expected encoding set to UTF-8, Response type set to "Parse response as JSON".


image


4) In the response body example, copy and paste the following JSON snippet into the field. Do note that you will need to change the customfield_1009 to the name of the field which actually stores your EPIC LINK. The next step will tell you how to find out what the name of the field is.


{

    "expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",

    "id": "10002",

    "self": "http://www.example.com/jira/rest/api/2/issue/10002",

    "key": "EX-1",

    "fields": {

          "customfield_10009": "DP-1"

    }

}    


5) In a SEPARATE Recipe (you can use this one), search for a JIRA issue which has an epic link based on the issue ID or key. Hit test recipe and you should have 1 successful job in your job output. View the job report and find the field which contains the epic link. In my JIRA instance, my epic link is stored under "customfield_10009", but your epic field name will probably differ.


image

image

Once you've found the custom field name, go back to Step 5 and change the name of the custom field to whatever your Epic Link custom field name is called.


7) Once that is done, you'll notice that you are able to map the Epic Link data pill (aka customfield XXXXXX) into other steps.

image




1 person has this question
Answer

CJ Wee

said about 6 years ago

Hi Mark,


While the Epic Link data pill is currently not accessible, this issue can be worked around using our HTTP connector. I have successfully implemented this for you while working with Kalpesh.


To others who are interested in this solution, you can follow the steps below.


1) Create a HTTP connection to JIRA. Give the connection a name, set authentication to Basic, and fill up the auth user and password which are your JIRA user login and password credentials. Do note that this needs to be the credentials of a JIRA System Admin


image


2) In the recipe where you need the JIRA epic link, create a new action, with application set to HTTP. The action will default to "Make REST request".

Give the request a name (up to you to decide), and add the Request URL as shown below. The highlighted portions in the URL should be changed to your JIRA hostname (url) and JIRA issue key (or ID) respectively. For the JIRA issue key (or ID), you can map a data pill into that portion of the URL instead of hard coding the value.


image


3) Next, leave the Request body empty, Expected encoding set to UTF-8, Response type set to "Parse response as JSON".


image


4) In the response body example, copy and paste the following JSON snippet into the field. Do note that you will need to change the customfield_1009 to the name of the field which actually stores your EPIC LINK. The next step will tell you how to find out what the name of the field is.


{

    "expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",

    "id": "10002",

    "self": "http://www.example.com/jira/rest/api/2/issue/10002",

    "key": "EX-1",

    "fields": {

          "customfield_10009": "DP-1"

    }

}    


5) In a SEPARATE Recipe (you can use this one), search for a JIRA issue which has an epic link based on the issue ID or key. Hit test recipe and you should have 1 successful job in your job output. View the job report and find the field which contains the epic link. In my JIRA instance, my epic link is stored under "customfield_10009", but your epic field name will probably differ.


image

image

Once you've found the custom field name, go back to Step 5 and change the name of the custom field to whatever your Epic Link custom field name is called.


7) Once that is done, you'll notice that you are able to map the Epic Link data pill (aka customfield XXXXXX) into other steps.

image



Login to post a comment

Still can't find your solution?

Send us a ticket, we will try our best to assist you with your problem

Documentation
Developer's Library
Tutorials
eBooks
Product Hour
Product Blog
Workato Blog
Product updates
Customer Stories
© Workato 2022   Privacy   Terms   +1 (844) 469-6752
  • Documentation
  • Workato Blog
  • Product Blog
  • Solutions
  • Forums
  • Tickets
  • Log in
  • Return to Workato
Topic views count