JirAI: Remote Development and privacy
JirAI supports Remote Development: the UI runs in JetBrains Client, while Jira requests and credentials stay on the host.
What runs where
- Client
The JirAI tool window, dialogs, editors and settings pages.
- Host
The connection to Jira, your credentials and the proxy settings.
What travels between client and host
The API token you type in the client's sign-in dialog travels to the host once, at sign-in, and is stored there; it is not stored on the client.
Files you attach are read on the client and streamed to the host, which uploads them to Jira; downloads travel the other way and are saved on the client.
All Jira requests are made by the host, so the host's proxy settings apply.
Your issue list filters are stored in the host project; the folder you last saved an attachment to is stored in the client.
JetBrains Marketplace installs JirAI on both sides as needed.
Differences under Remote Development
The Project tool window does not offer Push to Jira; use the button or the context menu in the Markdown editor. See Push Markdown docs: Remote Development.
Privacy
JirAI has no telemetry, analytics, usage statistics, crash reporting or error submitter.
Your credentials are sent only to the exact Jira site you signed in to, never to any other address, including look-alike addresses.
Avatars are loaded over HTTPS, without credentials, from the host that Jira names for them: Atlassian's avatar service or Gravatar.
Attachments and thumbnails are loaded from your Jira site.
Avatars and thumbnails are not saved to disk; they are kept only until you close the IDE.
For what is stored where, see Where JirAI stores credentials.