Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Create Individual JIRA Tickets for Individual Tasks Generated

Saviynt_Savvy
Regular Contributor
Regular Contributor

Hi,

I need the solution for the below use case:

Whenever a Birthright rule is triggered for a user, the birthright rule will generate a few tasks like,

1. Create an Account Task for Endpoint_X.
2. Add Access Task for Entitlement_A in Endpoint_X.
3. Add Access Task for Entitlement_B in Endpoint_X.

Whenever the Birthright rule triggers these tasks will be generated.

I need help on achieving the below REQUIREMENTS and I am facing the ISSUES mentioned below:

Requirement 1:
----------------
The requirement is all the tasks should be seperate and shouldn't relate to other tasks.

Issue:
When I see the " Pending Tasks", one of the task among 3 tasks are becoming PARENTTASK and all other tasks are being associated to it.

Requirement 2:
---------------
The requirement is, in JIRA 2 seperate tickets generated for Entitlement_A and Entitlement_B bringing the Dynamic values of Entitlements like "${entitlement_value}" instead of hardcoded values like "Add Access Ticket".

Issue: Using below CREATETICKETJSON, only one Ticket is generated for all the Add Access/ Remove Access type tasks generated.

Create TICKET JSON:
--------------------------------------

{
"call":[
{
"name":"call1",
"connection":"acctAuth",
"url":"https://xxxxxxxx.atlassian.net/rest/api/3/issue",
"httpMethod":"POST",
"httpParams":"{\"fields\": {\"project\":{\"key\":\"SP\"},\"summary\":\"${if(task.tasktype==1){'Add Access Ticket'}else if(task.tasktype==3){'Add Account Ticket'}else if (task.tasktype==2 && (allEntitlementsValues==null || allEntitlementsValues.isEmpty() || allEntitlementsValues=='')){'Remove Account'}else if(task.tasktype==2 && (allEntitlementsValues!=null || !allEntitlementsValues.isEmpty() || allEntitlementsValues!='')){'Remove Access'}else{'unknowtask'}}\",\"issuetype\": {\"name\": \"Task\"},\"reporter\":{\"id\":\"${user.customproperty8}\"}}}",
"httpHeaders":{
"Authorization":"${access_token}"
},
"httpContentType":"application/json",
"ticketidPath":"id",
"unsuccessResponses":{
"message":"Failed"
}
}
]
}

I have NO issue with the 'user.customproperty8'.

Please help on achieving the above 2 requirements.

Thanks

 

 

5 REPLIES 5

SowmithriV
Regular Contributor
Regular Contributor

Hello @Saviynt_Savvy, can you please tell me how are you generating the Create Ticket JSON from the user update rule? Can you please share the condition that you're using?

if user customproperty11='yes', assign the entitlement of a particular endpoint.

do we have create ticket action to be added in the user update rules? @Saviynt_Savvy 

I want to create a ticket for every disable task triggered from the User Update Rules 

I see no action like "create a ticket" is there in the user update rules.

SowmithriV
Regular Contributor
Regular Contributor

Correct. How are you triggering the Create Ticket JSON? @Saviynt_Savvy . That's exactly what I want to understand.