Hi!
Could you add the ability to enter in elapsed days (non-working days) into the predecessor field? This would be similar to the e#d in duration. Thank you!!
Kind regards,
Helena
Sign in to see the current vote count, add your own vote, or leave a comment.
Predecessor Field Enhancement to Support Elapsed Days. There is a critical need for Smartsheet to incorporate the ability to link from working days to elapsed days within the Predecessor Field. This enhancement is not just a convenience but a necessity for comprehensive project management.
The integration of elapsed days with predecessors is a feature that has seen consistent demand over the years. Its absence significantly hampers our ability to accurately track project timelines, especially in our industry where work progresses continuously across both working days and weekends and holidays.
Please seriously consider the long-term benefits and user satisfaction that this enhancement will bring.
Community, if you don't have the time to leave a comment please vote up the most applicable existing comment.
Please add this feature! It would be incredibly helpful!
+1 for this feature request, very important feature.
Extremely important feature! There are many threads with this topic, but this seems most recent so hoping I can bump it here.
My constant headache is that I manage many tech projects with weekend migrations - but migrations always have go/no-go dependencies, so I want to keep my predecessors in place in case anything shifts upstream.
If a row has no dependencies, using elapsed time to override non-working days works just fine. But if the row has a predecessor, it's impossible to force the START date to begin on a non-working day.
PLEASE FIX THIS!!
In the Community discussions I see 4 years of comments on multiple threads asking to add the use of elapsed time in predecessors - why hasn't this been implemented yet? Even when both the predecessor & the active task both have a elapsed time Duration, it still calculates the lag time in working days. So frustrating when my project is based on dependencies between different groups that have different working hours.
I've run into this issue where by the days I want a task to lag by is an elapsed number. E.g. Predecessor 380FS + e90d. The elapsed day function works well in the duration field.
The idea is to be able to schedule a task with lag or delay elapsed days. Eg. 110FS+ e30d.
In the Pharma industry, my business relies on being able to schedule items 30, 60, 90, or even longer out for stability related activities. The team has to rely on searching the number of business days for those lengths of times and isn't always exact due to holidays, site shutdowns, etc. It would be much easier for them to have elapsed days. Also, if any preceding activities move, this still remains the standard - their math may not align with new dates and thus throwing off their timelines.
Please add feature to be able to use elapsed days as a predecessor lag, as can be done with Microsoft Project for when I have tasks that reflect calendar days (i.e., regulatory timelines).
Wow, this request has been since 2022 and till now this has not been implemented. This is very important for activities that is happening even on weekends whereby there will be predecessors that either working only on normal working working hours of Mon-Fri. With recent issue with Smartsheet, putting just d as predecessor if duration is elapsed days, does not work. Consequently, using it vice versa, that is, a duration of normal working day and having to use elapsed days as predecessors.
This combination doesn't work with current version of Smartsheet. It used to work, but now it doesn't. I raised this issue, but I was asked to have a workaround to have a dummy lag of Normal days or weeks and make this as predecessor of the Elapsed days Duration. This creates longer Activity lines and reviewing the predecessors creates confusion unless you named it properly or put a Comment on it. It should work like this… Duration: e30d, Predecessor: 100FS +4d or 100FS +1w… Currently, 4d or 1w lag are not calculated correctly with this combination.
Agree this function used to work properly and suddenly something changed which also affected prior entered information. There has not been any clarity as to what changed or why.
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…
The Core Issue with Contact Columns Smartsheet Contact columns are fundamentally not reliable because they don’t represent people consistently. The same person can appear as a name in one place and an email address in another, depending on user status, permissions, ownership, or whether the data is viewed in a sheet,…
