Storing and Indexing JSON in JIRA Cloud

[Hugh Kelley]

Every new issue in our JIRA has a JSON document that is associated (details from the security alert that is associated with the issue).  Sizes are usually about 7 KB, but could be larger, depending on the details in the alert.

We currently attach this .json file to the issue at creation time (issues created via n8n workflow). 

Unfortunately,

1. this .json file is not indexed by JIRA, nor by any Marketplace apps we have yet found
2. the attachment is not always viewable in JIRA mobile app (some are too big?)
3. the attachment is never rendered as JSON (web or mobile), so it can be cumbersome to navigate.

Are there any suggestions as to how we can insert this JSON data into each issue in a way that doesn't clutter the issue's main tabs, is full-text indexed, and JSON-rendered when it is displayed (perhaps on an alternate tab)?

[Aaron Pavez _ServiceRocket_ · Accepted solution]

Hi @Hugh Kelley 

Looks like it's not possible. JSON or other files are not indexed by Jira cloud.

https://jira.atlassian.com/browse/JRACLOUD-1210

If you want, you can create a feature request here:

https://jira.atlassian.com/projects/JSWCLOUD/issues/JSWCLOUD-8507?filter=allopenissues

This is a stretch, but if you put the JSON in a doc. file? and use a 3rd party app to look into a doc file?

Regards

[Duong Nguyen Hong]

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 /rest/tgc/api/v1/grids/{gridId}/issue/{issueIdOrKey}

No need to overhaul your existing workflow — just add one extra step after issue creation.

1. Full-text indexing & JQL search
This is probably the biggest win. TGNG columns have an "Index data" option — once enabled, you can search across all issues with JQL like:

issue in grids("Security Alert", "cve_id~CVE-2024-1234")

Something a Jira attachment will never support.

2. JSON rendering
Use a Textarea column configured with Wiki Markup mode. You can then store the JSON inside a {code} macro, which renders it cleanly and makes it easy to navigate - on both web and mobile.

3. Not cluttering the issue
TGNG has a "Show Grids in Tab List" option, so the grid stays tucked away in a separate tab and only shows up when someone actually needs it.

Two approaches depending on your JSON structure:

* Quick option: One Textarea column with the full raw JSON wrapped in a {code} block - easy to set up, readable, and indexable.

 

* Structured option: Parse out key fields (severity, source IP, timestamp, CVE ID, etc.) into individual String/DateTime/Number columns, each with Index data enabled. This gives you much more granular JQL filtering down the line.

Feel free to give it a try, you can install Table Grid Next Generation directly from the Atlassian Marketplace. And if you have questions or want help setting up the grid config or the n8n integration, feel free to reach out - we're happy to help!