I had a similar request with the hopes that the Scenarios tool might be updated to have this feature. I just saw today that API v2 is being developed, but the one thing I really hoped would be there is a field for parent_ticket or the like.
The idea here is that our organization uses a parent ticket to create many child tickets for each action that must be performed for that parent (Tasks are not an option as they are very poorly made visible to agents).
Example scenario with the API:
1. A ticket comes in for a new employee
2. Using the API and some web or desktop tool I've created, I create a series of child tickets (typically 8 for new employees) just by pressing one button! It would GET the info from the parent and put what I want in to the child, and the children would have an API field that says parent_id = *that new employee ticket id*
We have exactly the same requirement as Reese.
Within our organisation we have a new employee workflow that is triggered from an external system which creates a number of tickets for various support teams to complete.
* User ID Pass
* Account Permissions
* Building Security Access
* Laptop / Desktop Hardware
We should then have an overarching parent ticket that can then be used to track these linked child tickets.
I feel that the lack of functionality within the API is a major oversight as both Reese and I cannot be the only ones requiring this functionality. Parent / Child Relationships are basic functions within any ITSM platform.
I also cannot see how difficulty it would be as it API endpoint for tickets is already available and it should just be a matter of exposing the parent_id as a writable field.