Configuring Integration for Jira Project Filtering
To assign Jira projects to incoming tickets, configure the following:
-
Modify the Before Provisioning Rulet to contain the logic to filter which Jira project the tickets are assigned to.
For example, you can have a use case where you create tickets in a Jira project with an ID of "33" where the application is Slack, and a Jira project with an ID of "50" where the application is Okta. Then for all other applications the tickets would be created in a Jira project with an ID of "1".
Note
In the below example, Slack and Okta are considered to be configured as a ManagedResource for the integration in question.Copyfor (AccountRequest accReq : Util.iterate(plan.getAccountRequests())) {
if (accReq.getApplicationName().equals("Slack")) {
plan.put("serviceDeskId", "33");
plan.put("requestTypeId", "33");
} else if (accReq.getApplicationName().equals("Okta")) {
plan.put("serviceDeskId", "50");
plan.put("requestTypeId", "50");
} else {
plan.put("serviceDeskId", "1");
plan.put("requestTypeId", "1");
}
} -
Modify the values for Request Type Id and Service Desk Id, located under the Ticket Creation section, to read the modified values from the Before Provisioning Rule rather than the default hard coded values.
Request Type Id: $plan.arguments.requestTypeId
Service Desk Id: $plan.arguments.serviceDeskId
-
Update the Identity Security Cloud Status to Atlassian Server Jira SDIM Status, located under the Status Mapping section, as per the status being received from multiple objects.