This idea has been archived, contributions have been disabled 

Hi Marek, thank you for posting this idea, and although I do understand your point here, we're closing this post without further action as it has not gathered a lot of votes during this time. The reason we haven't implemented stricter dependencies between due dates for the cards, is that the boards were designed with an Agile or 'Flow' methodology in mind, rather than a strict waterfall/dependency based methodology. But we may still get back to this further down the line if we start to hear more input like this.

Comments (4)

Hi Marek!
Thanks for your feedback! At least we hope that dependencies can give you some value at least. :-) We are very happy that you give us this input now as it gives other customers the chance to also vote and then give us indication to whether this is asked for by many of our users. Right now we don´t have any direct plans on connecting due dates this way between cards but we continously go to Ideas for input for future work.
Best regards
Silvija

Changing the way we work with Ideas, thus updating the status of your idea in line with the new process. New process works as follows:

1. When you post a new idea that we consider valid, we will label it 'Open to vote for', so that it can be shared with other users and start gathering votes
2. Ideas that are older than a year that we haven't gotten around to implement and that have not gathered enough votes will be archived.
3. We keep some older ideas that we think are in line with something we are planning otherwise or that have gathered enough votes.
4. If there are duplication of ideas, we may archive one of them and keep another which can continue to gather votes.
5. Ideas that we are planning to implement will be moved into the category 'Accepted'

I do not understand how dependencies could have been implemented without automating date changes to successor activities - or at the very least making them easily identifiable as needing attention. This is a major gap that I hope makes the votes for implementation!

Hi Marek, thank you for posting this idea, and although I do understand your point here, we're closing this post without further action as it has not gathered a lot of votes during this time. The reason we haven't implemented stricter dependencies between due dates for the cards, is that the boards were designed with an Agile or 'Flow' methodology in mind, rather than a strict waterfall/dependency based methodology. But we may still get back to this further down the line if we start to hear more input like this.

DIMELO - innovation management specialist