Does it store my Jira data?

No. Every chart queries Jira live as the person viewing it and keeps the result only in memory while the dashboard is open — nothing is written to storage, on Atlassian or anywhere else. Each gadget runs with the viewer's own permissions, so a chart can only ever show issues they already have access to.

Do I need to know JQL?

No. Basic filters let you pick projects, issue types, statuses, assignees, and more from dropdowns. JQL is there when you want it, but most charts never need it.

Can it chart custom fields?

Yes — both system and custom fields are available once they have values in your results, including number fields like story points.

How many issues can a chart use?

Large queries are capped for performance, and a site admin can set the limit. If your query exceeds it, narrow it with filters or JQL so the chart reflects the data you care about.

No data showing

If the chart is empty, work through these:

• Check the query actually returns issues — the editor shows a live match count as you build it.
• Make sure the fields you put on the axes have values for those issues; a field that's empty everywhere has nothing to plot.
• Click ↻ Refresh to re-query Jira in case the issues changed since the chart loaded.

A field is missing

If a field you expect isn't in the picker, it's usually one of two things: the field is empty across your current results, or it hasn't been loaded yet. Use Reload all fields to fetch the complete field list. Custom fields appear once at least one matching issue has a value for them.