When a user is disabled, Jira does does not create a separate ticket using the workflow

The disconnected apps are now grouped together in a single ticket, rather than generating two separate tickets for the disabled operation of the two disconnected apps as mentioned in link below we have a similar issue. We have more than 200 disconnected applications , and the client is not allowed to create 200 separate SDIMs

https://developer.sailpoint.com/discuss/t/atlassian-jira-sdim-behavior-when-user-has-two-disconnected-applications/111845

We have developed a workflow intended to create Jira tickets exclusively for disconnected sources. However, it is currently generating tickets for both direct connectors and disconnected sources. Our requirement is to create tickets solely for the disconnected sources.

Is there a way to filter out and create only for disconnected sources in the workflow?

Hi @Pkkumar ,

Inside the loop step, you can get the source information for each of the account by calling get-source | SailPoint Developer Community API. “Get Accounts” step will have the sourceID information which you need to pass in the above API. Then use “Compare Strings“ operator to check the type of connector as below. If it’s true, then call JIRA APIs to create ticket.

Please find the attached workflow JSON for your reference

DisconnectedAppsticketcreation20251029.json (4.9 KB)

Thanks, @Theja. I have adjusted the workflow as a JSON, and it executed successfully. However, the Jira ticket isn’t being created; instead, a manual task is generated.

Below is the workflow and the JSON. Is there something missing? Additionally, we have an authoritative source delimited, and we do not want to create a ticket for that either. Is there a way to filter it out?

JiraticketDisconnectedApps.json (5.2 KB)

Hi @Pkkumar ,

Can you change below highlighted step to “compare Boolean”?

Change as below

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.