Hi ​@matias.raimondo 

This is a known limitation of the current Lucid Jira integration, not a misconfiguration.

• Similar limitations exist for other fields like Epic Link, which may not behave as expected depending on the context or integration permissions.
• Jira fields may not behave identically in Lucid, which can limit interactivity and autocomplete capabilities

To learn more - Field not included in the "Selected fields" for Jira integration | Community

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

Hello ​@Humas1985 thank you for your reply, do you know if it is intended to do this integration?

Thank you

Currently, things do not support loading or suggesting existing Jira labels when creating tickets, so this is intended behavior at this time.

Regards

Hi ​@matias.raimondo, thanks for your post and thank you ​@Humas1985 for chiming in!

Indeed, Lucid doesn’t currently import label values from Jira, but we’re very interested in your feedback and committed to continually improving our products. Please feel free to create an idea 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: 

Cheers!