Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.loopiq.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Use Plain English SQL Generation

​
What this does

Plain English SQL generation helps analytics users turn a natural-language question into a SQL query for LoopIQ Analytics. It is designed for governed analytics workflows, not unrestricted database access. Use it when you want to explore data, create a custom chart, or build a metric without writing SQL from scratch.

​
Before you begin

Make sure:
  • your organization has access to LoopIQ Analytics
  • your role can use custom charts or analytics query features
  • the data you want to query is part of the approved analytics schema
  • you understand the business question you want to answer

​
Generate SQL from a question

  1. Open LoopIQ Analytics.
  2. Go to a custom chart or metric-building page.
  3. Open the Plain English SQL generator.
  4. Type the question you want to answer.
  5. Review the generated SQL.
  6. Review validation messages or warnings.
  7. Run the query only after confirming it matches your intent.
  8. Save the chart or metric if the result is useful.

​
Example questions

You can ask questions such as:
  • Show work items created by month for the last six months.
  • Show open incidents by severity and team.
  • Compare completed stories across recent sprints.
  • Show release certifications by status.
  • Find average cycle time by work item type.

​
Guardrails

LoopIQ validates generated SQL before execution. The generator is intended to prevent unsafe operations and restrict access to approved analytics tables and fields. Some tables are intentionally blocked, such as organization subscription data or internal organization records. User profile analytics tables that are approved for reporting may be available depending on the analytics schema.

​
Tips

  • Ask one question at a time.
  • Include the time range you care about.
  • Include grouping fields such as team, status, month, or severity.
  • Review generated joins carefully before saving a chart.
  • If validation blocks a query, rephrase the question or choose an approved metric source.