Duong Nguyen Hong Insider

Hi @GIOVANNI ASCIONE , Thanks for sharing the details of your current project! The 4-level access-request cascade is a great example of how MLC dependencies can be critical to your workflows, especially when ScriptRunner validators and post-functions rely on the app's Java APIs. To clarify the current situation on Cloud:…

I'm from the Visionade team. Jira does not natively support creating a column chart on a dashboard that groups issues by month and status. However, you can achieve this by using Visionade. Visionade allows you to build custom reports with various chart types, including column charts, and then embed them directly onto your…

Hi there, You are right, Jira's native Description field does not easily support dynamic or structured tables that appear automatically upon issue creation. It can be a significant limitation when you want to enforce a consistent data input structure. I am from Table Grid Next Generation team. Please note that our app does…

Thank you very much! @Sandro Santos I've added you as a participant to the ticket: https://tablegrid.atlassian.net/servicedesk/customer/portal/1/SOLV-9942 We're always here to help. Please don't hesitate to share any additional information that might help us better understand the issue, and we'll continue working with you…

Hi @Sandro Santos I'm Duong from the Table Grid Next Generation team. I can confirm that on Jira Cloud, our app currently supports Grid Custom Field as a standard Jira custom field. To help us better understand your use case and provide the best possible assistance, I have opened a support ticket on our portal on your…

Thank you very much @Swathi Acharya

Hi @Sandro Santos I'm Duong from the Table Grid Next Generation team. If I understand correctly, you're trying to configure a Select List column using Dynamic Options with Jira fields as the data source. You would like the Select List to display only the options belonging to the current field context of the issue, correct?…

Hi @Amir Hakakian My comment was deleted by @Dave Rosenlund _Trundl_.... Anyway, thank you so much for reaching out and raising a ticket with us via our Portal! I’ll do my best to provide you with the best possible support. Many thanks, Duong

Hello, I'm from the Table Grid team, and all three pain points you mentioned can actually be addressed with Table Grid Next Generation (TGNG). Instead of attaching the .json file, your n8n workflow can push the alert data directly into a Table Grid on the issue right at creation time, using the TGNG REST API: POST…

Just adding a follow-up to my original post — still exploring options here. If anyone has experience with Khoros-based communities and API access, would love to hear how you approached it. Thanks!

Feels free to try it on the Marketplace Table Grid Next Generation. Don’t hesitate to reach out if you need any support in achieving your use cases.

Hi @chickpeafilae, Great question! This is a common pain point we hear a lot. Jira's native custom fields are single-value by nature, which makes it really hard to capture transaction-like data (multiple line items, running totals, categorized entries) directly on an issue. I'm from the Table Grid Next Generation team. We…

Hi @Elbert Grigoriy , Glad the Work Item Statistics gadget worked for you! If you want something more advanced and flexible with a visual chart, I'd recommend Visionade - a reporting and dashboarding app for Jira Cloud. From the thread, it sounds like there are still a couple of gaps with the native gadget approach: The…

Hi @Ramu Trudy is right - displaying individual checklist items as separate columns in JQL list view isn't something native Jira (or any app) can do, since it's a platform-level limitation. That said, I'm from the Table Grid Next Generation team and wanted to suggest a slightly different approach that might solve the…