So my use case which appears to be similar to yours, in terms of using subitems to get an overall range of dates and timelines rolled up, runs into an issue right off the bat. There is one rather large looming caveat though that I also just realized after my initial excitement of cracking the code… This automation, not being a custom one, does not actually work for subitem fields… I was devastated as I went to go plug the automation in, thinking I’d finally figured out something that’s been bugging me for ages… only to find out that it doesn’t support subitems yet. Also, something obvious in hindsight, but discovered while experimenting for the sake of this post… if you set up the circular logic of adjusting a date field from timeline changes as well as adjusting the timeline field from date changes, the board is really not sure what to do, and your dates are going to just keep cycling through and never sit static after you make a change to one or the other.If the Due Date is July 22nd, and the Timeline is Juy 4th to July 22nd, changing the Due Date to July 20th wil adjust the Timeline to July 2nd to July 20th, and not July 4th to July 20th. On the inverse side of this, if the automation is set up to adjust the timeline based on the due date changing, it slides the entire timeline relative to the adjustment, and doesn’t just trim down the remaining time to be accurate.If Due Date is July 2nd, and the timeline is July 1st to July 3rd, changing the timeline to be July 1st to July 4th will adjust the Due Date to July 3rd (it doesn’t care if they have the same date or not, essentially). Because it is adjusting the date or timeline, and not actively setting it, that also means that if you’re due date is not set up as being your timeline’s end date (again there still doesn’t appear to be any monday-created automation that allows for setting this) and is set differently for some reason, then changing the timeline will still relatively adjust the due date.So when the timeline moves forward by 4 days, the due date (if set) will move with it automatically. This appears to be because the formula is ‘adjusting’ the due date, and not setting it. If the field is blank, it will not set anything within the field.
#Date on timelime update#
If you set it up to update the due date field when the timeline is changed, you need to also manually add the due date (the first time). It does not create something from nothing.I was able to set it up so that altering either the Due Date field or the Timeline field would change the other one, and at last I have a solution for my own problem with this… albeit not a fool-proof one. “Adjust this date to reflect the changes made in this other date of the same item” Specifically, the Dependencies automation of: It’s in the Dependencies section and not the Due Dates section though. In looking for a thread to upvote (and finding yours) as well as again following up by looking through the automation formulas, I actually ended up finding a possible fix… in the Automation Center, with a formula that isn’t possible currently with the basic customization. However, I’ve often been frustrated by both the column types and the automation when looking for solutions. Hey I’ve been looking for a similar solution for a while as well, in terms of having date fields get set based on timeline fields.
0 kommentar(er)
