Hi Adrian,

I’m one of the product managers that supports our Lucid Cards for Jira integration. Our current dynamic table feature supports the behavior you are describing for tasks or higher hierarchal levels (such as stories, features, epics etc.). If you select “Sprint” as a column and drag a Jira Card over into the sprint you want to associate the card with, it should sync back to Jira and assign that Jira task to that sprint. 

This feature will not work for subtasks because Jira does not support assigning subtasks to a sprint that is different from the Parent task. We cannot make changes in Jira that Jira doesn’t allow. To support this workflow in the future, I’d recommend using normal Jira tasks or stories that have an Epic as their parent. Then you will be able to assign each individual task to a sprint and visualize the tickets by Parent.

Please let me know if you have any additional questions or concerns! We always love to hear from our customers.

Thanks,

Spencer Cowley

Hi Spencer,

I think you may have misunderstood my request - I understand the current functionality, but my point was that this isn’t an effective solution if you’re using sub-tasks (there’s more shortcomings with that anyway, I’ll do that as another topic). I’m not trying to add a sub-task to a sprint, just Story level backlog items, but the view we use for standups has to display the sub-tasks...and if we’re using Lucid like we would a physical whiteboard (and less like JIRA enforced things) then this would be something we can easily do. Grab a post-it off the wall and put in the sprint. Done. That’s what we’re trying to do in this scenario.

What you’re suggesting is a workaround due to the way your software works, which I understand, but it isn’t a good solution to the problem. Having to change views on the table to support adding a backlog item to the sprint, and then change it back again so that we’re got a view that we’d actually work with in the standup is unnecessary steps. The irony, of course, is that in JIRA we’re just switching from  the backlog view to the Board view, and maybe that is the approach we’d need to mentally model for ourselves using this - but it’s not the way the “add to sprint” capability is marketed.

Sub-tasks in JIRA is a mess anyway, but it’s popular, so having a view that handles that but also allows you to add items to the sprint would be a useful feature to have if we’re to really move away from working in JIRA at any point beyond the refinement stage.

Hey Adrian - thanks for going more in depth on this. I think I misunderstood your original request and would love to talk through this and your other feedback about Parents. I sent you a message to see if you’d be open to hopping on a call to talk through that feedback - looking forward to hearing from you.