This idea has been archived, contributions have been disabled 

Hi Damien,

thanks for your feedback. As Tomas explained it is unlikely that we will implement the ability to affect the whole plan by the change of the due date on an individual card. However, there are other ways we are thinking about tying the cards and activities closer together. Things that we are considering:
1. Being able to have the activity dates constrain the dates of cards - making it impossible to set a due date for a card that is outside the dates of the activity.
2. Making it visible on the activity that there is a card that is outside the dates - thus making it possible for the project manager to see and discuss with the team what the consequences would be of not completing this card within the scope of the activity. Maybe the card needs to be pushed to another activity, maybe the card needs to get a higher priority etc...

Either way we agree that the logic should be that cards and activity dates are linked and that if this changes (ie a card falls outside the scope of "its" activity) there should be a discussion between team and management on how this should be handled.

Best regards,
Karolina

Comments (3)

Anonymous
Anonymous

Anonymous

Level
0
Score
0

We are at the moment not considering having Card dates affect the dates of the Activities. We are however, working on showing more information about the Activities (e.g. in the Activity swim lane view) and have the date picker reflect these "limitations".
We might consider making it possible to edit the dates of the Activities from the Board.
It is unlikely that we will automate this since it is hard to see the consequences for the Plan as a whole from the board view, especially when we are implementing dependencies between Activities.
A date on a Card could potentially and perhaps unintentionally affect the whole plan.

Hi Damien,

thanks for your feedback. As Tomas explained it is unlikely that we will implement the ability to affect the whole plan by the change of the due date on an individual card. However, there are other ways we are thinking about tying the cards and activities closer together. Things that we are considering:
1. Being able to have the activity dates constrain the dates of cards - making it impossible to set a due date for a card that is outside the dates of the activity.
2. Making it visible on the activity that there is a card that is outside the dates - thus making it possible for the project manager to see and discuss with the team what the consequences would be of not completing this card within the scope of the activity. Maybe the card needs to be pushed to another activity, maybe the card needs to get a higher priority etc...

Either way we agree that the logic should be that cards and activity dates are linked and that if this changes (ie a card falls outside the scope of "its" activity) there should be a discussion between team and management on how this should be handled.

Best regards,
Karolina

A fairly simple solution might work well here: if a card is tied to an activity and a due date in the card is entered that exceeds the due date of the (tied) activity, simply give a warning message "the start or due date you've entered is not corresponding to the start or due date of the activity. Are you sure this is correct?".

That will at least 'force' you to rethink, but you still have the option to continue.

I can't imagine this solution will be really hard to implement, but it will take some pain away for sure...

DIMELO - SocialCRM software editor