Hi,
We have a scenario where the user’s end date is modified in the Auth source and subsequently updated in SailPoint. In such cases, we need to create a Jira ticket. For instance, John Doe’s current end date is 09/10/2025. If the end date changes to 02/12/2026 in the Auth source and is updated to the identity attribute in SailPoint, a Jira ticket should be created for all disconnected sources, ensuring a separate ticket for each source.
Is there a way to do this?
Thanks,
Hello and welcome to the community!!!
Have you looked at using workflows for this? In workflows there is an action to make an API call that you could use to submit your Jira ticket. In Workflow you can build the needed data you want in the ticket.
If you do not have access to Workflows another option would be to use the search API and run a batch job from a util server. This design would have search that the end date was undated via events as long as the data is being updated in a down stream source using attribute sync. This will log in the Events in search. Once you have the search defined you can then use that to pass in the payload to the Search API. Once you convert the response from json into a object you can then parse each object and submit the ticket to Jira via api.
These would be the two options I would look into to build our this workflow. Please let us know if you have any questions about these 2 options.