8000 Add Feature: Children/Related cards · Issue #709 · wekan/wekan · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add Feature: Children/Related cards #709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
hmrodrigues opened this issue Oct 13, 2016 · 17 comments
Closed

Add Feature: Children/Related cards #709

hmrodrigues opened this issue Oct 13, 2016 · 17 comments
Labels
Feature:Cards:Related

Comments

@hmrodrigues
Copy link

It would be awesome to have some kind of relation between cards, like a link two or more cards
@xet7
Copy link
Member
xet7 commented Jan 15, 2017

@hmrodrigues

How it should work? What would it be used for?

@hmrodrigues
Copy link
Author

@xet7
You can have basic relations, kinda like related issues.
In my case for dependencies.

@xet7
Copy link
Member
xet7 commented Jan 15, 2017

@hmrodrigues

Does changing one affect the other one someway? Could you provide step by step instructions how this should work and how it would be useful?

@hmrodrigues
Copy link
Author

@xet7 Not really. The process is just like labels. In Card1 you select Card2 as a related card.
This would be useful to relate card that aren't on the same label ,for example, you have a task that splits into four microtasks. Two of them with the label FrontOffice, one with BackOffice and the another with Core. With the relations, you can have all those four microtasks connected.

@xet7
Copy link
Member
xet7 commented Feb 13, 2017

Maybe something like this in kanbanflow?

subtasks_at_kanbanflow

@hmrodrigues
Copy link
Author

@xet7 Yes kinda like that

@xet7 xet7 changed the title Children/Related cards Add Feature: Children/Related cards Apr 2, 2017
@xet7 xet7 mentioned this issue Jun 27, 2017
Closed
@xet7
Copy link
Member
xet7 commented Jun 27, 2017

Moved to here from #1092

From @yarons

I'm not sure I fully understood how to define a relation between two cards, lets pretend my card is about putting an entire footwear, I have another card for putting socks on and then I have a card for putting shoes on.
Can I define the relation between them to be that I can't go on with the footwear card until I finish the socks and shoes cards?

Thanks!

@anrras
Copy link
anrras commented Sep 7, 2017 •
edited
Loading

I understand is like more the powerup "helloepics" from trello Link

@yarons
Copy link
yarons commented Sep 9, 2017

@xet7, although you can wear shows without socks, the relation to socks in that case is a blocker, a task that unless completed the wearing shoes action may not be executed (completely or partially).

@xet7 xet7 mentioned this issue Nov 29, 2017
Closed
@xet7
Copy link
Member
xet7 commented Nov 29, 2017

Moved to here from #1364

From 8000 @TNick

I want to implement categories for cards. Each card would belong to exactly one category that is, by default, (un-categorized).

The category would determine the aspect of the cards:

  • background color;
  • presence / absence of a border;
  • the shape of the minicard;

(v2) Each category can host a template for the card that might be applied to cards at any time.

Categories would be organized in a tree, with one (possibly) inheriting properties from its patent(s). The tree of categories should be edited in right side panel by going to Menu->Categories. The panel needs Add sibling, Add kid, Remove, and items can be re-parented by drag-n-drop. Deleting a category deletes all its kids. All cards that ware in a deleted category are reassigned to (un-categorized).

Changing the properties of a category (aspect of cards) can be done in same panel; each should allow inheriting from the parent / using the default for top level categories.

Changing the category of a card should be possible when the card is expanded.

I'm looking into implementing this feature for my personal use and, if needed, I could contribute it to the project. This is my first attempt at Wekan, so any ideas or suggestions about how to go about this are highly appreciated.

@xet7
Copy link
Member
xet7 commented Nov 29, 2017

@TNick

Yes your features are welcome to Wekan. Please look at Developer Documentation and add any questions and info or your progress to this issue. Thanks!

@xet7
Copy link
Member
xet7 commented Nov 29, 2017

Related #211

@TNick TNick mentioned this issue Dec 1, 2017
Open
@andresmanelli andresmanelli mentioned this issue Apr 18, 2018
Merged
@TiibCD
Copy link
TiibCD commented May 16, 2018 •
edited
Loading

Hi all,

Indeed it would be great to have dependencies between cards.
For example Card A cannot move until all related cards aren't "done". Or just a feature to see a relation between cards parent/child would also be great like the "Helloepics" plugin

@d3dbit
Copy link
d3dbit commented May 27, 2018 •
edited
Loading

Great feature.

+1 to @TiibCD 's comment:
"For example Card A cannot move until all related cards aren't "done". Or just a feature to see a relation between cards parent/child would also be great like the "Helloepics" plugin"

@xet7
Copy link
Member
xet7 commented Jun 24, 2018

Children cards implemented by @TNick at #1723

@xet7 xet7 closed this as completed in cc753cf Jul 5, 2018
@beingshashi
Copy link
beingshashi commented May 27, 2019 •
edited
Loading

@xet7 : Can it be possible to auto import parent checklists to child card automatically - whenever a new checklist is added to the parent card?

@xet7
Copy link
Member
xet7 commented May 27, 2019

@beingshashi

Please add new Feature Request issue with screenshot mockup and description how it should work.

@rasos rasos mentioned this issue Jun 12, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Cards:Related
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@xet7 @anrras @yarons @hmrodrigues @beingshashi @TiibCD @d3dbit
0