two programming codes for reports - predecesors | Community
Skip to main content
Level 2
August 19, 2025
Question

two programming codes for reports - predecesors

  • August 19, 2025
  • 2 replies
  • 338 views

I need two programming codes for reports. I'm hoping someone here can help me out before I submit a ticket. 

 

1) I want the predecessor task(s) to show as the predecessor number (w/ hyperlink) as well as the date due. If I can only get one, the date due is a higher priority, but I still need the hyperlink.

2) I need the predecessor's predecessor task names (also w/ hyperlinks). We have a "readiness date" which has several predecessors and I need to be able to see what those are in a report.

 

Thanks in advance!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Kurt_Jones
Community Advisor
Community Advisor
August 20, 2025

Lisa,

 

If you have a task report (or even within a project plan view) if you click on the Predecessor you're able to see the information you're describing, such as the task name, the planned start and end dates of that item.  Within that dialog view you can click the predecessor heading (Task 3...) and it will take you to that task.  Not the best user experience but the Predecessor field it part of a tile component that was built and not really another way to get to that information except through this tile/dialog that was created.  I hope this was somewhat helpful 

 

 

If my response answered your question, please mark it answered, so others can find the answer
LisaMc1Author
Level 2
August 20, 2025

We already have this in place, but the data behind it is not reportable so it does not solve the issue. We need the planned completion date of the predecessor and the predecessor's predecessors for a central planner to see consolidated work in the queue.

kautuk_sahni
Community Manager
Community Manager
September 1, 2025

@lisamc1 just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

Kautuk Sahni
LisaMc1Author
Level 2
September 2, 2025

No. As stated above, this is not resolved.