This idea has been archived, contributions have been disabled
I know this has been discussed in the past, so please excuse me for bringing it up once again. I'd like to reiterate that it's a good idea and there's a good bit of interest in this topic.
Team members ask me regularly about dependencies on cards. They want to show relationships between cards, and these are almost always dependency relationships. We need a way to connect cards and note dependencies between them.
The flat architecture is okay as-is, but the board functionality would be richer if this functionality existed.
We have "defined" dependencies between cards using comments in the description as well as a naming convention for the card, but it's very easy to overlook these mechanisms. Would be nice to have a way to bundle a few cards together and have the bundle represented in a way where it's easy to see the relationship.
Hi Susanne!
Thanks for sharing your idea with us! This is something we hear about from time to time and our recommendations is that you create sub activities to which you connect your cards to. This way you can then use the feature to group by activities on the board and with this visualize cards that belong together. Hope this tip could be useful for both you Susanne and Rick! See attached file.
Best regards,
Silvija
Greetings Silvija, doesn't sound like your workaround is appropriate in the case when Plan Activities have been assigned? It would work if the User can assign to a Card multiple Plan Activities. Regards, Brandon
Hi Brandon!
Can you give me an example of how you work with cards and activities in your project? It would help me to get a better understanding to how you work. Any screenshot would also help. :)
Best regards
Silvija
Greetings Silvija, please have a look at the attached image file. Regards, Brandon
When working with many kinds of development there is a nomenclature used in many other systems where Features consists of User Stories, which consists of Tasks.
I fully agree with what has been requested above, but to further detail teh requirement it would be nive to have the possibility to have dependencies and types on cards.
Best regards
Henric Trolme
I would also like this functionality. We have people in different teams that need to wait for eachother to work on a card. With the suggested workarounds this is still prone to error (people simply don't read all details). I also thought of a workaround to assign a card on a hidden board or to put it in a hidden status column, but it cannot be done.
Hi Susanne,
This has been implemented and is live in the service.
Thanks,
Som
Som stated
Nick voted
Marc voted
Jennifer voted
an anonymous voted
Nat voted
an anonymous posted a new comment
an anonymous voted
Henric posted a new comment
Silvija posted a new comment
Brandon posted a new comment
Silvija posted a new comment
Brandon voted
Brandon posted a new comment
Silvija stated
Silvija posted a new comment
an anonymous voted
Oliver voted
an anonymous voted
Rick posted a new comment
Rick and an anonymous voted
Susanne posted a new idea
Som Chakravarty
Hi Susanne,
This has been implemented and is live in the service.
Thanks,
Som