Question 1

Can Ana use JQL?

Accepted Answer

Yes. Ana constructs JQL queries dynamically based on the natural language question, which lets it filter by status, assignee, sprint, component, label, custom fields, or any combination. Server-side filtering keeps API usage efficient and respects Jira permissions.

Question 2

Does Ana see Jira custom fields?

Accepted Answer

Yes. The connector discovers every custom field configured on your Jira projects. Ana can filter, aggregate, and join on any custom field just like built-in fields. This is especially useful if your workflow encodes customer IDs or severity levels in custom fields.

Question 3

How are Jira credentials secured?

Accepted Answer

OAuth refresh tokens and API keys are encrypted in TextQL's credential vault and injected by our egress proxy at the network layer. Ana's Python sandbox never receives the raw token value. Refresh and rotation happen outside the sandbox and are fully audited.

Question 4

Does Ana respect Jira project permissions?

Accepted Answer

Yes. When using per-user OAuth, every API call runs under the calling user's Jira identity, so project and issue-level permissions are enforced by Atlassian on the server side. Ana cannot see issues the user could not otherwise access.

Question 5

Does this work with Jira Data Center?

Accepted Answer

Yes. Both Jira Cloud and Jira Data Center are supported. For Data Center, an admin whitelists your self-hosted Jira domain in the TextQL admin console instead of api.atlassian.com. Authentication uses PAT or basic auth with encrypted storage.