Jira Spoke update issue

[Mark Davies]

Has anyone used the Jira spoke Update Issue. 

The form input in the Flow designer needs to first require a Jira ticket number (required field). This makes sense but is most likely going to be stored on the Snow record (e.g. Correlation ID or similar). The problem is that the rest of the form needs to dynamically read the metadata of that ticket in Jira. It wants to determine what project and Issue type the Jira issue that ticket is in order to determine what Jira fields can be mapped (makes sense that is how Jira is configured). I was thinking I could maybe use a direct ticket reference in editor temporarily in order to complete the setup of the field mapping and then replace it with a reference to the Correlation ID when done. Anyone know if this would work or will the form reset? 

Unfortunately the editor is also errorring on this scenario. It appears that it is making the correct API calls to Jira to get the metadata but it looks like the spoke component is truncating the response internally and cannot parse the result. The error occurs in the “Get Creatable Fields” action of the spoke. Anyone else seen this or have a workaround?

[Faisal Reza]

I am having this exact same problem, I can't use a "dynamic" Jira ID from the ServiceNow Record to bring up the list of additional fields.

I do get the additional fields if I fill the flow with a static Jira ID but then it makes the flow pretty useless....

[PLakin1]

I know this is multiple years old, but I was encountering this issue as well and couldn't find a doc or this thread. I put a ticket in with support and that's exactly what they advise you do. Put an existing correlation ID into the mandatory trigger field, which will make the Additional Fields option available, change the ID to a dynamic value, by selecting a pill for instance, then finish your flow and save it.

If you ever go to edit the flow you'll have to do the same thing again. 

[Mathieu Lepoutr]

Hi Mark

If you're looking to dynamically read metadata from a Jira ticket and encounter issues with the Jira spoke's Update Issue action or the "Get Creatable Fields" action, yYou can try using a direct ticket reference temporarily to set up the field mapping and then replace it with the Correlation ID. 

1. If the spoke encounters errors, such as truncating the response or being unable to parse it, reach out to the integration's support or community forums for assistance. They might have workarounds or fixes for this issue.

Consider exploring alternative integration options like Exalate. Exalate is a third-party integration platform for synchronizing data between Jira instances, I have been using it quite a lot.