BryanT.38843 (Customer) asked a question.
I've got a case open for this but figured I'd post here as well in case anyone is experiencing a similar issue.
I'm working on an Offboarding workflow which will use the Jira Service Desk "New Request" event card as the trigger. I've got the first part of the flow setup such that it confirms the change type, finds the Okta user corresponding to the employee ID provided on the Service Desk ticket, composes a message contain info from said users' okta profile and then comments it on the ticket. There will obviously be more steps eventually but this first iteration should at least let me know it's working when the comment appears.
Unfortunately, neither the "New Request" or "New Request in Queue" event cards appear to be working despite the Jira Service Desk connector reporting that the authorization was successful and the connection is health.
Hi Tim, thanks the case was resolved. For anyone coming across this in the future I ended up using the standard Jira new issue event card with a JQL query to filter based on the project and issue type rather than the event card built specifically for Jira Service Desk. Despite verifying the permissions were correct and completely rebuilding the flow using JSD we couldn't get it to work.