How can we get the value of the custom fields?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2020 01:28 AM
We used Jira spoke v2.5 to integrate ServiceNow SAFe with Jira software.
We have one problem that couldn't get the value of the custom field in Process Jira Webhooks of Subflow.
How can we get the value of the custom fields?
[Prerequisite settings]
- 1.Create a project in Jira software and add customization fields(JiraID) to this project
- 2.Use "Flow >trigger jira" to pass data from ServiceNow SAFe to Jira Software
- 3.Use "Subflows > Process Jira Webhooks" to pass data From Jira Software to ServiceNow SAFe
Detail of setting
- 2.Use "Flows >trigger jira" to pass data from ServiceNow SAFe to Jira Software,
The setting as follows:
- 3.Use "Subflows > Process Jira Webhooks" to pass data From Jira Software to ServiceNow SAFe
The setting as follows:
[Test After setting]
- Create a story in the ServiceNow
- The Same story is Automatically generated in Jira software
[About log as follows]
- The log of Flow > Trigger jira >action
- The log of Subflows > Process Jira Webhooks >action
- Labels:
-
Workflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2021 11:11 AM
Guys I found the solution to this problem.
The solution is not to modify API resource. I spent many hours going down that rabbit hole and it did not work out.
The solution is to keep the out of box API processing so that you still get all of the default objects. That part works great and you don't need to change it.
What you need to do is in say the first step of your flow create a new action. In that action just add a JSON parsing step. Grab the payload that is coming from Jira and that will contain your custom field/s, and generate the output based on the json payload. There is a ton of extra unused columns that will come in with the payload so you can either include everything or like I did, you can modify the json payload to remove the unneeded fields.
Then in your flow, when you need to access the custom field, instead of trying to pull them from the default objects where it does not exist, you can pull the custom fields from the output of your action where they will exist. Whalla! Magic!
Now if I could only figure out how to parse out the changelog object! haha but that is a problem for another time.
Don't forget to subscribe, ring the bell and put your likes if you found value!!
Regards,
Shawn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2021 09:56 AM
Hi
Can you please provide some screen shots , i'm trying to do something similar.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2023 06:45 AM
yes can you provide screenshots of this please?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2023 11:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2023 11:12 AM