Rollup Based on Child Project Tickets

[Travis Hill]

Im trying to figure out the basic structure / setup of a rule. Essentially I want to enable a rule (either schedule based or when a ticket is linked / removed as a child) that will index the projects that are children to the ticket and then correlate that into a custom field on the parent.

So for example:

Ticket 1 has three children

• One in Project A (called alpha)
• One in Project B (called beta)
• One in Project C (called corner)

In the main field on the parent it will house the project names (not the project keys). So it basically needs to say ok this ticket has a child ticket in Project A so I need to add alpha to the custom field. But the field needs to add or remove from the custom field accordingly.

Thanks in advance!

[Trudy P Claspill]

Hello @Travis Hill 

What type of field is the custom field that will hold the Project Names?

Another scenario you have to consider is if the child ticket in Alpha remains a child of Ticket 1 but is moved to a different project; i.e. project delta.

And another couple of scenarios to consider are what happens if the child is deleted entirely, or archived?

[Travis Hill]

Hello thanks for reaching out. It is a multi-select field