I am trying to inspect GateTask objects and am getting stalled in dependencies.
Currently a dependency in a GateTask only contains a target task ID. When trying to inspect the target task, I am unable to see the various ancestors of the task, including:
* complete folder path
* releaseTitle
* phaseTitle
* nested parent taskTitles
I would really appreciate the ability to incorporate ancestor details when requesting a task by ID. Alternatively, perhaps this information could get added to the GateTask dependency data?
by: Rauha R. | about a month ago | API & CLI tools
Comments
Thank you for the idea. Could you share the situations or use cases where ancestor details (release title, phase, folder path, parent tasks) for a GateTask dependency are important. Is it mainly for debugging, reporting, or something else?
It's primarily for reporting. My automation reports on tasks by type and my users would like to see the set of releases+tasks a particular release is gated on.
Thank you for the follow-up. We’ll continue to monitor upvotes from the broader customer base. In the meantime, you can create custom API endpoints with Jython script objects as an alternative approach. You can find more details here: https://docs.digital.ai/release/docs/how-to/declare-custom-rest-endpoints .