Skip to main content
hamburger menu
+ Create a topic
Answer

Duplicated column in "dynamic table"

  • October 9, 2024
  • 3 replies
  • 45 views
M
Forum|alt.badge.img+1

hello, there is status in jira called “Ready for review”, the problem is that depending where you are in JIra (settings, workflow, board) this status is presentes as:

READY FOR REVIEW

Ready For Review

Ready for reviwe
It seams that Jira is not case sensitive, … I’ve seen similar things about “In progress”, but for some reason “In progress” does not causes issues in Lucid.
In our case, dynamic table shows two column one named: Ready for review, the second one is Ready For Review. 
During moving cards between columns in dynamic table, we can observe, quite often, that jira cards jumps from “Ready for review” column to the “Ready For Review” there and back, sometimes even 2-3 times… 
If we do not make any operation on content of dynamic table, then we can observe stable positions. Items are never divided between mentioned columns, all of them are are places in one of those “duplicated” part of table.

Could you fix it? 

Best answer by Leianne C

Hi @MW007, thank you for posting in the community! I’ve checked this with our development team and this is currently expected behaviour. 

However, we’re very interested in your feedback and committed to continually improving our products. Please first search the Product Feedback section of this community (with the filter Topic Type = Idea) to see if it’s already been submitted. If so, please add any additional details you’d like and upvote the request - this consolidation helps to refine feedback and properly capture the popularity of the request.

If no one has submitted this idea yet, please create one of your own and be sure to include details about your use case or what you’d like to see in this experience. This will also allow other users with similar requests to discover and upvote it, then add details of their own.

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

Thank you for sharing your feedback and please feel free to let us know if you have any questions. 

Comments

Humas1985
Lucid Legend Level 10
Forum|alt.badge.img+24
  • Humas1985Lucid Legend Level 10
  • Lucid Legend Level 10
  • October 9, 2024

Hi @MW007 

This issue likely arises from:

Jira's case-insensitive status handling not being properly interpreted by Lucidchart, or
Slight variations in status name storage across Jira's system.


Try these options and give a try:
Standardize status names across Jira, ensuring consistent formatting "Ready for Review" in workflow, board settings, and elsewhere.
Or 
Utilize JQL queries to normalize the status name when importing issues into Lucidchart, such as status in ("Ready for Review", "READY FOR REVIEW", "Ready For Review")

---------------------------------------------------------------

We also look forward to hearing from other community members and associates, who may have alternative suggestions that could better address your requirements.

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

Huma || Lucid Legend
M
Forum|alt.badge.img+1
  • MW007
  • Author
  • October 11, 2024

I’m interested in seeing issues in the 'ready for review' status, regardless of their naming. So my JQL is more like:

status not in ("removed", "waiting")

I’m glad it captures different 'ready for review' statuses. It would be great if the dynamic table could map all of them into a single column, but as you know, there aren’t many customization opportunities with the dynamic table.
Reconfiguring Jira is also not an option, as it’s used by many teams. Moreover, here's an example: when you create or edit workflows, Jira shows all statuses capitalized, so all I can add or remove is 'READY FOR REVIEW,' and I have no control over how it’s represented in their system (lowercase or uppercase). Therefore, enforcing consistent formatting in Jira isn’t a viable approach, as we already face internal inconsistency.

In other words, this is an opportunity for Lucid developers to offer an option to map different statuses into a single column in the dynamic table.

Regards

Leianne C
Forum|alt.badge.img+15
  • Leianne C
  • Lucid support team
  • Answer
  • October 14, 2024

Hi @MW007, thank you for posting in the community! I’ve checked this with our development team and this is currently expected behaviour. 

However, we’re very interested in your feedback and committed to continually improving our products. Please first search the Product Feedback section of this community (with the filter Topic Type = Idea) to see if it’s already been submitted. If so, please add any additional details you’d like and upvote the request - this consolidation helps to refine feedback and properly capture the popularity of the request.

If no one has submitted this idea yet, please create one of your own and be sure to include details about your use case or what you’d like to see in this experience. This will also allow other users with similar requests to discover and upvote it, then add details of their own.

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

Thank you for sharing your feedback and please feel free to let us know if you have any questions. 

Level up your skills & unlock exclusive perks!

Join Lucid Legends
Lucid Software Inc. Supplemental Community TermsAccessibility statement

Get Started

Products

Solutions

Resources

Company

Privacy Legal Cookie privacy choices Cookie policy
© 2025  Lucid Software Inc.