Lucid Card dependencies without Jira

Hi ​@andrewharder 

There is no built-in dependency system for tasks, making it difficult to establish relationships between them or automate status updates. We need to rely on workarounds to visually represent dependencies, these solutions are limited and don't offer true automation or task-linking functionality per your ask.

We can also wait to know from other products experts from the community with their suggestion other than simulating.

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

Hi ​@andrewharder, thanks for posting in the Lucid Community! Sorry for the delay here. Thank you ​@Humas1985 for your help here, you’re correct! 

​@andrewharder the dependencies/link issue types are populated from Jira or Azure DevOps, so can only be created when using Jira or Azure DevOps cards. Otherwise the line defaults to a basic line rather than a dependency line. 

We’re still very interested in your feedback and committed to continually improving our products. If you’re willing to share, we’d love to hear more details about your use case or what you’d like to see in this experience within this thread.

I’ve also converted this post to an idea so that it’s visible to others within the Product Feedback section of the community - from here, they can upvote it and add details of their own.

Finally, for more information on how Lucid manages feedback via this community, take a look at this post:

Hi, has there been any updates on this? Any chance this was an added feature? if not, what are the recommended work arounds?

Hi ​@rvassilatos, thanks for checking in and bumping this thread!

To answer your question directly: there haven’t been updates to this functionality over the past year. Native dependency mapping, like standalone “Blocks” and “Blocked by” links on Lucid cards without a Jira or Azure DevOps sync, isn’t on our near-term roadmap right now. We have logged the request in our backlog so we can keep tracking customer demand, but our team’s focus is on other areas of the platform at the moment.

We know that’s not the answer you were hoping for. In the meantime, here are a few ways to show and manage dependencies natively in Lucid:

• Connector lines: Draw directional lines between your cards and double-click a line to label it “Blocks” or “Blocked by.” Styling critical dependencies with a distinct color, thicker weight, or dashed line makes the path easy to spot at a glance.
• Tags or color-coding: Use Lucidspark tags or card colors to mark items as “Blocked.” This lets you quickly filter your board and see what’s waiting on prerequisites.
• A “Blocked” swimlane: If your cards are in a Dynamic Table, Timeline, or Matrix, adding a dedicated “Blocked” swimlane keeps dependent work visibly separated until the preceding work is done.

Note: these are manual workarounds, so they won’t update automatically as cards move.

We really appreciate you sharing your feedback. If native dependencies make it onto our roadmap, we’ll update this thread.