Skip to main content

How to View JSON in Jira — Fields, Entity Properties & Pasted Payloads

· 4 min read
NGPilot

Half the debugging in a Jira-integrated stack ends at the same place: a wall of braces. A webhook payload pasted into a comment, a config blob in a custom field, entity properties an integration app quietly wrote onto the ticket — the JSON is there, on the issue, but reading it means scrolling and counting brackets. Here are three ways to actually read it, from free-but-painful to a proper graph view inside Jira.

Quick answer: Install JSON Graph Viewer & Visualizer for Jira and open any issue — the panel finds JSON in issue fields and entity properties automatically, and a Paste JSON tab accepts any raw payload. Each source renders as an interactive node graph you can expand, collapse, pan, and zoom, with a syntax-highlighted code view alongside.

Method 1 — Read It Raw (the Default Pain)​

Jira shows long field values in a plain text view. For a short config object that's fine. For a real payload it means mentally tracking nesting depth across a scrolling wall of braces — and the failure mode is silent: you miscount a level and conclude the wrong node holds the value you need.

Good for: a one-line {"flag": true}. Beyond that, you're doing in your head what a tree view does on screen.

Method 2 — Browser Dev Tools (Developer-Only, Off-Ticket)​

Anyone technical can open dev tools, run a fetch against the REST API, and eyeball the response in the console. It works, and it's the right move when you're already mid-debug.

What's missing: it lives outside Jira, so it only works for you, right now. The JSON nobody else can see is the JSON that stays misunderstood — a support engineer, PM, or teammate opening the ticket tomorrow sees nothing. And a payload that only exists in a comment thread is one careless edit away from a broken bracket.

Method 3 — a Graph Panel on the Issue (Recommended)​

JSON Graph Viewer & Visualizer for Jira adds a panel to every issue that turns JSON into an interactive node graph. It reads JSON from three sources:

  1. Issue fields — the panel scans for fields whose content parses as JSON (REST payloads, API responses, config blobs). One match renders immediately; several matches get a dropdown.
  2. Issue properties — the entity properties other apps store on the issue, normally invisible in the UI, rendered as graphs.
  3. Paste JSON — a syntax-highlighted editor that graphs what you type, live. Paste a webhook payload or API response and fold everything you don't care about into collapsed n items nodes.

The view-mode dropdown switches between Code (formatted and highlighted, like your editor), Graph (the node diagram), or both side by side — read the payload above, see its shape below. Everything renders in your browser with read-only access: nothing is stored or sent anywhere else, so customer payloads stay in your Jira session.

A Payload to Try It On​

Paste this into the Paste JSON tab — it's the shape of a typical webhook body with a nested custom field:

{
  "issue": {
    "key": "PROJ-142",
    "fields": {
      "summary": "Checkout API returns 500 on empty cart",
      "priority": { "name": "High", "id": "2" },
      "labels": ["backend", "payments"],
      "customfield_10123": {
        "service": "checkout-api",
        "environment": "prod",
        "traceId": "a1b2c3",
        "retries": 3
      }
    }
  }
}

In graph view, collapse fields and the whole subtree folds into one node — expand just customfield_10123 when the config is what you're checking. That's the whole workflow: fold what you know, open what you're verifying.

Which Method Should You Use?​

NeedUse
Check a two-line flagRaw field view
One-off debug in your own browserDev tools + REST API
JSON that lives on the issue and must be readable by the whole teamJSON Graph Viewer panel

The third row is the one that compounds: the payload stays attached to the issue, everyone who opens the ticket sees the same readable structure, and nobody has to count braces at 3am. Install JSON Graph Viewer & Visualizer for Jira and open your messiest integration ticket to see the difference.

Try JSON Structure Viewer for Confluence

Visualize JSON as interactive structure diagrams — free for up to 10 users.

Get it on the Atlassian Marketplace

Related guides