Can I pull information from a scenarios history of a request processed through Fusion?

[DawnmarieD]

We lost some of our requests during a specific time (May-December 2024). Looking to see if I can pull either the original request or the request that was created by Fusion before another scenario created a task/subtask/issue from the request in another project.

Any help would be helpful. I am not fluent in API, JSON or any dev. lingo. But, I can copy and paste and finagle my info. to make it work.

Thank you in advance,

=D

[Lawson02]

What do you mean by lost? What happened to the requests, were they deleted?

If they were deleted there is a recently deleted section in the setup section.

[DawnmarieD]

Thank you. Based on the dates it is longer than 30 days and cannot be restored via WF.

The process works like this:

Webhook > Fusion (scenario 1) creates a Issue and puts it on a Landing Project in WF > Fusion (scenario 2) pulls from that Landing Project and creates a task, sub task(s), issue(s) from that issue.

Initially everything worked fine, I must have made a change at some point in WF that resolved the issue when the task was created from scenario 1 and now those issues no longer exist they were deleted from WF. I must have changed it back so now I have all the issues after December and everything is back to "normal".

Because the initial request comes via a web page and we convert it in Fusion to a WF request then convert that request to a task, sub task and issue, the original information from the first issue is lost and may have since been changed at the WF level. I need to pull into a report the information from those original requests but do not have them to get that information. I would like to pull the history from Fusion to recreate those issues from May - Dec.

I hope this helps in providing more information about the process and what I am trying to achieve. I also recognize this may not be possible but trying to do my due diligence.

Thank you again,

Dawnmarie

[Lawson02]

This would probably be a question for support. I would submit a ticket and see what they can do about it.

[kautuk_sahni]

@DawnmarieD Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!