'Create Issue' action in flow designer using JIRA spoke showing error

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-19-2022 02:54 AM - edited ‎10-19-2022 03:05 AM
'Create Issue' action in flow designer using JIRA spoke showing error - 'Bad Request. The current operation ended in state: ERROR' , even before testing the action or setting any values, or when we try to select this action in a flow, this error pops up.
Any help would be appreciated. Snap attached below:
Regards,
Sudhangshu

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2022 02:59 PM
This is due to your Connection Alias being blank. This field needs to be populated in order to grab info from Jira. Project Key depends on Connection Alias for the Dynamic Choice to populate with data. Likewise, Issue Type depends on Project Key for the Dynamic Choice to populate with data. Additional Fields depends on Connection Alias, Project Key, and Issue Type to query the fields available for selection.
In order to select a Connection Alias, you will need to first need to either configure the OOB one, named Jira (sn_jira_spoke.Jira), or create one by following this link: Create connection records for the Jira spoke - ServiceNow Docs

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-27-2022 12:31 AM
Hi,
The error is still there even if we select the connection alias. And it doesn't change.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2022 01:27 PM
Funny thing, this started happening to me too today. I have verified that the connection creds are correct and can even use it to import data with other actions... but am getting that same error today.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-08-2022 07:13 AM
Hi
I would advice you to populate the field.
Another route you can take is using Exalate. This will sync any entity to Jira, which could be really advantagous in this situation in my opinion.