Skip to main content
New Idea

Allow API to be queried for a Ticket's Predecessor / Successor Tickets

Related products:Freshservice
  • December 12, 2024
  • 2 replies
  • 54 views

Forum|alt.badge.img+11

As per the title, I’d like for there to be API methods introduced whereby you can grab details of whether a Ticket has any Predecessor / Successor Tickets in its chain, their Status, etc.

I think the Predecessor/Successor Ticket concept seems to exclusively belong to the Onboarding/Offboarding Modules at the moment.

This request comes about as, at present, automated Actions performed on Successor Tickets are always performed by ‘System’ which makes it impossible to trigger Workflows leading on from those Activities.

 

Should it be made possible for System activities to trigger further Workflows as per …

... then this Feature Request is less likely to be needed.

2 replies

Forum|alt.badge.img+11
  • Author
  • Skilled Expert
  • January 9, 2025

Just for clarification, this is currently all that you can get back from the API:

Neither give the individual Child or Parent Ticket Status or Predecessor/Successor info, forcing you to find a way to loop through each ID to get their Status externally from Freshservice.  Even upon doing so you still will not get any info about Predecessor/Successor state.

I suppose you could tell the Onboarding/Offboarding modules to set Successor tickets to something like a ‘Waiting on Predecessor’ Status which more easily identifies something as a Successor ticket but it’d be great if the API just gave us this in the first place, similar to how Task Dependency conceptually works.


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

I agree :)