JirAI: FAQ and known limitations
General questions
- Does JirAI support Jira Server or Jira Data Center?
No. JirAI works with Jira Cloud only.
Jira Server and Jira Data Center use a different API and sign-in model.
- Is JirAI free?
Yes. You need no license, trial or subscription to install and use JirAI.
- Does JirAI collect telemetry or send my code anywhere?
No. JirAI has no telemetry or analytics, and it does not read or send your source code.
Requests with your credentials go only to the Jira site you signed in to.
Markdown documents are sent to Jira only when you push them.
- Why does the issue list show only issues from the last 365 days?
Every search and filter in the issue list covers issues created in the last 365 days.
To open an older issue, type its key, for example
DEMO-123, in the search field.See Search and sort.
- Can I connect to several Jira sites?
No. JirAI connects to one Jira Cloud site at a time.
To switch sites, sign out and then sign in to the other site.
- Can I see delivery metrics such as cycle time?
Yes. Open a space with Space Summary and use the Reports tab.
Troubleshooting
- Why is the issue list empty after I sign in?
The list starts with the Assigned to Me quick filter and shows only issues created in the last 365 days.
If no such issue is assigned to you, the list reads Nothing matches the filters.
To see all issues, click Clear filters, or choose All Issues in the Filters menu.
See Filter the list.
- My AI assistant does not see the JirAI tools. Why?
The tools need the IDE's MCP server, which is off by default.
Turn it on in , configure your assistant with Auto-Configure and check Exposed Tools.
The IDE must be running with a project open.
- Why can't I edit a description?
The description contains content that has no Markdown equivalent, such as a table, a panel or an image.
Saving it from the IDE would lose that content, so JirAI shows the reason and an Open in browser link.
- Why is a board marked Limited?
It is a team-managed board.
Team-managed boards do not open in the IDE; choosing one opens it in Jira.
- Why does my Scrum board show only some of its sprints?
The Board tab shows a Scrum board's active sprint.
When a board has more than one active sprint, it shows the first and names the others in a notice.
When no sprint is active, the board is empty until a sprint starts in Jira.
- Why can't I create a branch from an issue?
Create Branch… needs the bundled Git plugin; when the plugin is disabled, the command does not appear.
When the project has no Git repository, the command is disabled.
- Why doesn't my commit message start with the issue key?
Check the following:
The key is added only when you commit with changelists, not with the Git staging area. Turn off Enable staging area in .
The name of the current branch must contain the issue key in capital letters, for example
DEMO-42-fix-login-timeout, and you must be signed in to the issue's Jira site.The key is added only to an empty commit message. A draft or a Git commit template is never replaced.
If the project's repositories are on branches of different issues, no key is added.
Start commit messages with the current issue key must be selected in .
- Why does JirAI say I am not signed in, or that the sign-in was rejected?
JirAI shows Not signed in to Jira, or the sign-in was rejected. when Jira no longer accepts your API token, for example because the token expired or was revoked.
Create a new API token, then sign out and sign in again in the JirAI tool window.
- Where is my API token stored?
In the IDE credential store, which is the operating system keychain or the IDE's KeePass file.
Under Remote Development, it is stored on the host.
- How do I use JirAI behind a corporate proxy?
JirAI uses the proxy in .
SOCKS proxies are not supported: with a SOCKS proxy set, JirAI connects to Jira directly.
- How do I report a problem?
See Support for where to report it and what to include.
Known limitations
Jira Cloud only, with one site at a time.
Sign-in with an API token only; OAuth is not supported.
Issue list searches cover issues created in the last 365 days, except a search for a single issue key.
No JQL: queries are built from the filters and the search field.
Restricted comments and service-desk comments can be edited only in Jira.
Descriptions with tables, panels, media and similar content can be edited only in Jira.
Team-managed boards open in Jira, and a Scrum board shows only its first active sprint.
The Timeline tab of a space opens the space in Jira.
Branches, the current issue and the commit-message key work with Git only, and the commit-message key needs changelists, not the staging area.
In the details tab, custom fields, the reporter and the issue type are read-only.
Push to Jira works only on files with the .md extension.
Under Remote Development, the Project view does not offer Push to Jira; use the button or the context menu in the editor.