Improve the visibility into the task dependencies in the project sheet via function/formula or inbuilt capability to display dependent task names
Sign in to see the current vote count, add your own vote, or leave a comment.
This would be extremely helpful especially for large integrated project plans where the predecessor and/or successor are in an entirely different 'family' of tasks in the sheet (e.g. row 1262 is dependent on row 364 and 868). It would eliminate the need to jump around all over the sheet to understand what the predecessors and successors of a task actually are.
Another "yes please!" for this. I have developed a workaround but it has issues.
Another yes please from me.
@SSG will you explain your work-around?
@SSG Please, could you send us your work-around? It will be so helpful!
When you click on a call in the predecessor column, it shows the task numbers and names that are tied to that task. The successor column does not show this, which results in a lot of scrolling to understand the workflow. Please set the successor column up to display the task names the same way the predecessor column is set up.
In the dependencies table, it would be very valuable if the items listed the successors as the predecessors are labeled.
Summary of Issue All team members work a standard 7.5‑hour day, but only a portion of that day is allocated for project work (e.g., 25%, 50%, etc.). In Resource Management, however, the system currently interprets allocations as a percentage of the full 7.5 hours, instead of the project‑eligible portion of a person’s day.…
Dashboard widgets are currently mostly static. I can display counts and charts, but I cannot click into a specific part of a widget to drill into the underlying records. It would be a big usability improvement if widgets supported interactive drill-down. For example: Click a bar segment (or stacked segment) to open the…
IDEA: for Workflow automations, add a detailed "modification history" Currently, the Workflow Automation only lists the Created By, Created Date, Last Modified By, Last Modified Date, and Last Ran on. This is missing critical information. It doesn't show any changes to: Automation name Trigger conditions Actions Recipients…
