Skip to main content

Ability to link items multiple ways

It would be convenient to have the ability to link like parent, child, peer, predecessor, successor selectable from the item itself. After type selection one should be able to search for the item to be linked.

Status: Open9 comments

Log in to comment and vote

Comments9

  • Max

    •

    Oct 11, 2023

    This would be really helpful in my workflow. We manage financial services clients, who may have different solutions or strategies being implemented, (planning, investments, insurance, etc. ) Each of these solutions has it's own unique workflow.

    I could envision a Board with all of my clients as a Card or Milestone. I might move them through different status' as they progress through a sales cycle. I then create child cards as i'm planning the work for the client, which i then promote/move to other boards or workspaces depending on the solution.

    It would be great to maintain a link from the original parent (client) card, to the child (solution/strategy) card(s) on different boards, and vice versa.

    Not only would this help me visualize the client work from their "master card" but the specialists managing other boards/workspaces could also link back to the master card for additional context on the client and other work being performed.

    I originally encountered functionality like this in Trello through their "Attachments" feature. One attachment type is a Link. You can either paste a hyperlink to any site or page, or when you click into the field, you can search for the names of other cards to establish a one or two-way link. I found that this feature helped me navigate large and various boards rather quickly.

    • Vidas

      Team•

      Oct 12, 2023

      Max: what about "dependency" type relation. If I understand correctly the use case you've described, it should do exactly that - serve as a link between related items. Once all dependencies are finished you can close the major milestone/client project. Would this work?

    • Max

      •

      Oct 13, 2023

      Vidas: Hi, thanks for your response. I've been trying your idea. I think it is a bit of a workaround for what I have in mind. It get's the job done, but is a bit tedious to establish. Perhaps one way to make this process quicker is in the "Convert to Parent" process (I'm not psyched that it was buried in the meatball menu with the last update btw). Could a blocking/waiting-on dependency be automatically established between the two cards?

      I know this isn't a CRM system, but I guess what I'm trying to accomplish is something like "Set Regarding" a card/task to a client record. I've seen the idea of using Tags for client names, which helps for filtering. However, it doesn't really help to quickly navigate around an individual client's various cards

    • Vidas

      Team•

      Oct 19, 2023

      Max: out of our user base, I think most common scenarios for client work grouping are:

      • One board per client (best for mid sized projects)

      • One row per client and then one board of rows per client portfolio/location/etc. (best for small sized projects, standalone tasks)

      • One tag per client

      Next, I hear you regarding the complexity of making dependencies, we are actually in progress for taking a stab how to improve relationships. For now, our first target is synced copy. It has the most complexity and requires flexibility. Next will be dependencies for sure.

      Lastly, I completely understand that moving actions to context menu added friction for convert to parent action, but at least for now I see also quite a psotive win (which is a traded-off of course) in scenarios which are far more common, for example just opening and reading content of the item.

    • Max

      •

      Oct 20, 2023

      Vidas: I like the "row per client" idea. I'll experiment with that.

      Also, I only just noticed that you can access "Convert to Parent" from the Action Menu next to Child Item on the original Parent Item screen. That will help.

      I would vote to automatically create a "Waiting/Blocking" dependency between the two cards when "Convert to Parent" is utilized.

  • Vidas

    Team•

    Aug 28, 2023

    Wim Verloop peer is the most interesting one to me, how would you use it? Do two child items (same parent) are treated as peer?

    We already have at least predecessor/successor linking from item details where you can search. Child/parent missing though. Should we continue going same path in item details? Screenshot attached.

    • Wim Verloop

      •

      Aug 29, 2023

      Vidas: I would use it to plan / arrange tasks which can / should be done in parallel by different persons or teams but belong to the same parent.

    • Vidas

      Team•

      Aug 30, 2023

      Wim Verloop: why not use child items then? Maybe it is because you need to split them and place in different boards (but still keep aligned to one parent/root item)?

    • Wim Verloop

      •

      Aug 30, 2023

      Vidas: Yes that is exactly it. To clarify I would need a lot of text, if you think it could help, I can send you an e-mail with screenshots so you perhaps better understand what I'm trying to achieve.