Dynamic tables to support time-based fields outside of sprint
It would be great if Dynamic Tables supported some of the time-based fields (outside of sprint) in Jira. Either target end date or release.
I know you can do this manually with custom columns, but I’m not using Lucid/Jira syncing to do manual work. I want it to automatically populate. So a feature like this would really help with roadmapping and release planning, while minimizing manual work to sync across Lucid and Jira.
Page 1 / 1
Hi @user1234321, thank you for this feedback! 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.
We encourage anyone else who’s interested in this to upvote this post and share any additional details. For more information about how we manage feedback in this community, please take a look at this post:
@Ambar D - I am trying to visualize our product roadmap, but in a way where it is directly tied into Jira. I think Dynamic tables is the best way to do this, so I can set up a filter and easily pull in Jira updates / sync status. The goal is to do this based directly on data in jira (so not creating custom columns, etc).
The issue is displaying items in a way where I can show when we target releasing items over time. Sprints doesn’t work.
So ideally being able to read in the target end date and set columns by month, and/or set columns release, would allow us to visualize.
Hopefully that helps.
Hey @user1234321 - I’m the product manager here at Lucid over our Jira Cards, Dynamic Tables & Timelines features.
Have you had a chance to use Jira Cards in the timeline shape before? We recently added support for Jira Cards to be added to timelines and you can map your fields from Jira (such as Target end date) in Lucid to visualize the cards in the timeline based on those dates. Editing the cards in the timeline will also sync back to Jira so the date fields stay in sync. I think this feature will help you with the roadmapping use case and we’d love any feedback you have if you have a chance to try it out.
This help center article section walks through the steps to use a timeline and map your Jira dates correctly: Work with timelines in Lucidspark
We don’t have support yet for JQL query sync for timelines but this is something we are looking at adding in the next few months. Would this be helpful for your workflow?
Let me know if you have any additional questions or feedback!
Spencer
@scowley That is great to hear, I was not aware you recently added this (timelines is actually probably the better solution). I’m trying to follow the instructions under section “Sync Lucid date fields with a Lucid Card integration” to map the date fields, but I’m getting stuck at step 5.
It does not show an option to map fields, just to either import or create JIRA cards (see screenshot). I already have JIRA cards on this board, and when I import more, I still don’t see an option to map the date fields.
A JQL query would be very valuable so that it dynamically updates based on changes in JIRA.
@user1234321 Glad to hear that timelines would help. I haven’t seen this bug before, let me touch base with the team and get back to you.
In the meantime, could you see if you experience the same bug when using the card edit menu settings button? Here’s a screenshot that shows how to find that button:
I’ll let you know what I hear from the team!
Thanks,
Spencer
The card edit menu settings option seems to have worked. Thanks!
Good to know! I appreciate you making us aware of the issue and we will follow up internally to see if we can reproduce the issue on our side.
If you have any additional feedback related to Dynamic Tables, Timelines or Jira Cards, feel free to tag me in future posts in the community or send me a direct message. I always love hearing from our users and it helps us make a better experience for everyone.
A Lucid account is required to interact with the Community, and your participation is subject to the
Supplemental Lucid Community Terms.
You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
A Lucid account is required to interact with the Community, and your participation is subject to the
Supplemental Lucid Community Terms.
You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.