Hi Murjiani,

First, some helpful resources that I think will help you - dynamic tables and dependency mapping

How to Add a Dynamic Table

A Blog Article on Utilization of a Dynamic Table

Dependency Mapping

A Blog Article on Dependency Mapping

A quick gif with a couple of examples of how it all works together - hopefully this helps…

1. Generate a jql in jira - copy it
2. In Lucid select the jira integration diamond - select import
3. Flip the jql toggle first - then paste the jql - then select the magnify glass for search
4. Select the checkbox at the top to grab everything and then Import into Dynamic Table
5. Move the To Do column to the front
6. Click on the bottom of the card to show dependencies picked up out of jira
7. Ooops - task 2 is dependent upon task 1 so change the “in progress” to “roadblocked”
8. Move the Roadblocked column between To Do and In Progress

Hopefully this small example gives you everything you need. All of this scales according to your jql data. You can also link jira cards using the arrow mapping like any other shapes for relationships you don’t have defined in jira. I’ll do this at times when I want to link stories together informally.

Give it go!

Thanks,

Rick

One more thing - if you want to turn off the dependency mapping - just click the bottom of the card again and select the Keep line visible toggle to off. Sometimes that helps to clean up the mapping.

And if you want to turn it all off - select the link icon (looks like a jump-rope to me) and you get more options to quickly change all cards links by type or by issue…
 

Sorry for the multiple posts - but one other thought… unfortunately dependency line mapping isn’t as robust as standard line mapping (and even that could use some help). It can make a mess of your tables - turning on/off the dependency lines as needed (as noted in previous post) can help provide some clarity.

You can pull and twist a dependency line but that can get ugly - particularly if you move the cards around.

I noted using shape lines - and that can help - while not perfect because there’s not a perfect autopath - you can do some fairly decent manipulation.

Going back to my example - when shifting to roadblock the dynamic table reorganized and the dependency line just went straight through the existing card. You can manipulate it a bit but any future changes get ugly.

Adding a manual line between shapes initially does the same (goes through the existing card) - but you can easily grab the handle and make a very pretty line. Then turn off the ugly display of the dependency. Sometimes this may be a better choice if you’re presenting a diagram or taking a snapshot for a presentation.