Dependencies
complete
A
Avi Hercenberg
It would be great if we could set dependencies within records (ClickUp, coda, and Monday.com have this)
This would allow you to set if a record is dependent on another record before it can be started/completed to help further automate your workflow management.
Brian Dollen
complete
The dependency field type and our Gantt view were released during the What's New webinar last week! You can find all the details in the help article or the recording:
https://help.smartsuite.com/en/articles/8609918-dependency-field
https://help.smartsuite.com/en/articles/8610014-gantt-view
https://www.youtube.com/watch?v=lPM-Uiwz1yU
Threads Julian Dumitrascu
Let's use software that allows us to press a button in order e.g. to start following a conversation!
Loic LeMener
Thanks Jon Darbyshire for the sneak peek on dependencies yesterday. It looks promising! One thing I didn't see, which would be great is to have, is different outcomes when you finish a task that steer the user to different "next steps." This would enable us to build complex workflows. Thanks!
G
Gary Ford
Loic LeMener: yes - I agree
K
Karl Hosking
Would love to see this feature too, where the user can't input into Field B without fields [Field A, Field C, Field D] each meeting some form of criteria.
Thomas Barnekow
The fact that this feature is missing makes it hard, if not impossible, for us to select SmartSuite as a platform for project management. I would otherwise love to use SmartSuite for its other qualities.
Garrett Clawson
Definitely agree with @Loic LeMener's comment. It would be great to have automatic rescheduling of dependencies if due dates change on a particular task. (ClickUp does this really well.)
A
Adam Roe
Same for us. There is no project management without dependencies as all tasks are free floating without it
Loic LeMener
If possible having the dates "cascade" as part of the dependency would be awesome. So if I have several to-do's at different times for an upcoming meeting and I change the meeting date, all the dependent tasks move in reference to that meeting date. thanks!
Jon Darbyshire
in progress
Thomas Barnekow
Jon Darbyshire: Is there an ETA for that feature?
A
Alison White
Absolutely NEED this feature, would sign our entire organisation up immediately if dependencies and subtasks were improved. (if anyone knows a work around for now please do let me know!).
One thing I think that HIVE does very well (there aren't a great deal of things it does and can't wait to make the leap to SmartSuite as it is heads and shoulders above anything else seen/used), is its tasks and sub tasks and dependencies (and I don't think the Gantt chart development necessarily needs to be developed 1st) .
In SmartSuite the subtasks are hidden from view and sit "inside" a task and have very limiting functionality and visibility. Whereas with HIVE the subtasks are shown nested in the grid view as shown in the image. You click on each subtask and set a "if "receive data file" (subtask) is complete, unblock "load data file" subtask, ready to be worked on. It sends a notification to the person assigned to the next subtask in the work list to tell them that item is now ready to work on. It is the most important feature of all of our requirements. Even though all of our tasks have dates, we only use these as a guide/deadline and basically do anything in our workflow that is ready and available to work on and I currently can't find an easy way to solve this.
We have 250 tracking studies where our standard set of "fieldwork period" tasks (across ALL projects) recur on a monthly/quarterly or annual basis at varying days/dates/times/frequencies. When you set the dates for each subtask they are relational to each other and when you set the overarching "fieldwork" period to recur on a monthly basis (on say the 6th of every month in this case), the future recurrences of all the sub actions follow on inline from the previous months dates. It is very user friendly and really simple to set up.
There may currently be a very long winded way with formulas and automations to achieve what we are trying to, however I haven't found any solution yet.
I believe also in relation to recurrences, that if we were to set up each of our "subtasks" in SmartSuite as plain old tasks, the issue with using the automation (I believe) is that you would have to set each task to recur itself individually and we would only want all of our tasks for a given fieldwork period to recur once the last task for that period was complete, ready for the next period.
Load More
→