Unable to auto-create child work items when another issue type is created

Question

Hello, I have a JSM project with 3 different boards - Asset, CA , PTO. These 3 boards are dependent on each other so the automation rules will be a domino effect.

The issue type and request type share the same names as the 3 boards. Let me explain the workflow.

User will first create a ticket in the Asset board and fill in the details. Here, the automation check if there is an existing Service in the Jira Service (this is our Jira Assets / Objects, called Services). If there is an existing Service with the same name as the Asset ticket, it will revert the Asset ticket status to 'In Draft' and stops there. But it is no existing Service, it will create the Jira object in the Jira Service. The automation for this works and no issue.

Once all is ok, the Asset ticket will transit to 'In CA Review'. Here, the rule will automatically create the CA ticket in the CA board and the user fills in the details. Again, it will check for existing CA ticket with the same name as Asset ticket. If there is, CA ticket will be created. When the CA ticket in is Approved status, I want the Asset ticket to transit to 'In PTO Review'. This is where the automation has issue.

When Asset is in 'In PTO Review', it will create a new PTO ticket. The creation of PTO ticket works, but the creation of the child work items doesn't. For PTO, the PTO ticket will be the parent ticket and the Gate (issue type and request type) is the child work item and will be nested in the PTO.

Now, in order to tell the rule on how many child work items to create, the rule need to see the Deployment Type field value in the Asset ticket. If it is Internal, it will create 13 Gates, if it is external, it will create 10 gates. How do I set this up?

I currently have this as my rule set up but no child tickets are created. The end goal is to have the child work items created and nested in the PTO parent ticket.

Thank you in advance.

Akhand Pratap Singh_z78moi · Answer

@Nur Fatin , From your screenshot it says, no related work items could be found, why are using using branch here?

If you have already defined issue type at the beginning why using branch, as there is no issues found it doesn't work, also conditions didn't match.

Suggestion would remove branch if not needed and check your conditions once.

NOTE: It is showing success but it is not, it is not creating any work items as branch and conditions are not fulfilled

Nur Fatin · Answer

@Akhand Pratap Singh  it says success but no child work items created. can you show me which part i should edit, please? based on my previous screenshots. sorry, i didn't catch that

Akhand Pratap Singh_z78moi · Answer

@Nur Fatin , Can you share the Audit logs once?

Want to check if the rule is even triggered and if triggered where it stops.

Also Quick Question, When PTO is created, Automation is updating the Request type.

My guess is as you have added request type in the create Condition, this rule is triggered before the request types is updated.

Move that condition out from the triggered and add a separate condition for this at the same time if you are using Request type condition, add 2 action before this condition that is Delay and re-issue