Time Dependencies in Card Relations
In this article:
Overview
When you work a lot with card relations, then you might easily lose track of whether the deliverables such as subcards or cards in a previous-next relation. Most of the time, the work is delivered by other people or departments, and it can easily slip out of the required time frames.
To catch quickly whether something will not be delivered within the required time all dependent parent and previous cards will be marked with an orange exclamation mark.
Example: The orange exclamation mark next to the status icon indicates problems with card dates and other card relation issues.
After entering the card, we can find more information about the conflict in the card issues section.
Example: See the Card issues section for an explanation of the problem.
Possible time dependency issues
- The child card starts before the parent card
- The child card ends before the parent card starts
- The child card starts after the parent card ends
- The child card ends after the parent card
- The next card starts before the previous card
- The next card starts before the previous card ends
- The next card ends before the previous card starts
- The next card ends before the previous card
Relations do not have to be direct. For example, the grandchild card (child of another child card) can be in conflict with the grandparent card (parent of another parent card). The same situation applies to cards that are chained by previous-next relations.
What to do in case of card relations conflict? You can find out with the following examples.
Parent-child card relation conflicts
In the parent-child relation, there is a rule that the subcard must fit within the parent card’s time frame. That is, all subcards should start after the parent card starts and end before the parent card ends.
Let’s have a look at the example of a possible problem and its solution. We have two cards: the Parent card and the Subcard card. They are related with the parent-child card relation.
Example: The parent card ends on November 23rd, while the subcard starts on this day.
The subcard starts and ends after the due date of the parent card. We can see an orange warning in the card details section of the parent card informing us of the card issue.
The most convenient way to manage time dependencies is the Gantt Chart view, where you can adjust times using sliding and drag-and-drop. You can also do this by changing the dates on every card separately.
Example: Gantt Chart view allows us to manage card schedule in convenient way using drag and drop.
Next-previous card relation conflicts
The next-previous card relation is a logical dependency between cards. The previous card must be completed before the next card can begin.
Here you have another example of card relations conflict. There is the Printouts card as the previous card and the Hang up posters card as the next card.
Example: The previous card is so far behind the next one that it causes 4 time conflicts (the orange ones).
The most convenient way to manage time dependencies is the Gantt Chart view, where you can adjust cards using sliding and drag and drop. You can also do this by changing the dates on every card separately.
Example: Gantt Chart view allows us to manage card schedule in convenient way using drag and drop.
FAQ
Can date dependencies observation work across multiple spaces?
Yes, date dependencies observation can work across multiple spaces.
Can indirect card relations also create dependency conflicts?
Yes, card relations that are not direct such as “grandchild” and “grandparent” cards.
What kind of card relation can I create using Mind Map view?
You can create parent and child relations using the Mind Map view.
Was this article helpful?
Please, contact us if you have any additional questions.