Hi @TomaszBryla 

Lucidchart's native capability does not support custom fields and checkboxes for Jira Assets.

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

Hi @TomaszBryla, thanks for posting in the Lucid Community!

@Humas1985 is correct, however, we’re very interested in your feedback and committed to continually improving our products. 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. I’ve also converted this post to an idea so that it’s visible to others within the Product Feedback section of the community - from here, they can upvote it and add details of their own.

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

@TomaszBryla , @Humas1985 is correct, but thank you for the feedback!

Can you tell me more about the use case to include Jira Assets custom fields in Lucid?

Hi @Amelia W, @Humas1985, @Preston H 

Thank you for the quick response. The Project Management Office uses Jira to manage all the projects in the company. The organization structure is visualized in the Jira Assets (Insight) add-on. Each ticket has defined  different objects from the schema where the organization structure is built. The PMO would like to see those fields in Lucid Cards for Jira.

Regards
Tomasz

Adding Team Field would be a good addition. If the team name cannot be dynamically added then a text field with a uuid value of the team would work.

@Saurabh Sabat, thank you for the additional feedback!

I agree with adding Team. Here’s my use case.

We do user story mapping in Lucid with multiple product teams. Once it’s fleshed out we import into Jira to plan and execute. Most teams have their own Jira project, but some teams work on the same product so they differentiate based on the Team field.

When we convert the stickies into Jira issues we do it team by team - to import into each Jira project in turn - so we need to be able to specify the Team at that point so that, once imported, the issues appear in the appropriate product backlog (because each team’s Jira board is sourced using the value of the Team field).

@mpgoodin Thank you for your additional feedback!

Hi, I’ve got a Select List (multiple choices) type custom field in Jira that shows as unsupported in LucidSpark. Could this custom field type be added to the supported list?