JirAI: Settings reference

JirAI

Settings | Tools | JirAI

Account

The Jira Cloud account JirAI is signed in to.

Click + to sign in, or select the account and click − to sign out.

JirAI connects to one site at a time, so + is unavailable while you are signed in.

Resources

The JirAI documentation link opens this documentation.

See Sign in and manage your account.

Field Visibility

Settings | Tools | JirAI | Field Visibility

Lists the custom fields hidden from the issue details tab, one rule per row:

Site

The Jira site address, for example https://demo-org.atlassian.net.

Field name

A name shown in the table only.

Field ID

The field ID the rule matches, for example customfield_10020.

Scope

All projects, one project or one issue.

Target

The project key or issue key; empty for all projects.

Click + to add a rule in the Add Hidden Field Rule dialog, or select rules and click − to unhide the fields.

See Hide custom fields.

Doc Push

Settings | Tools | JirAI | Doc Push (current project only)

Preset

Choose Superpowers, spec-kit or None.

Doc kinds table

Lists your own kinds first, then the preset's kinds, with the Kind, Path pattern, Project key, Issue type, Labels and Components columns.

Kinds are tried from top to bottom, and the first match wins.

Path pattern

Matches the document path inside the project: * stays within one folder, ** crosses folders, and ? matches one character.

Targets

Set the project key, issue type, labels and components for each kind.

You can type names; JirAI resolves them when the Create form opens.

By default, JirAI picks the preset from the project's folders the first time you push a document.

The target columns stay read-only until you open the JirAI tool window while you are signed in.

See Configure presets in Settings.

Development

Settings | Tools | JirAI | Development

How JirAI names the branches you create from issues, what happens after you create one, and how it fills in commit messages.

Branch name

The template for new branch names.

Default: {key}-{summary}, which gives names such as DEMO-42-fix-login-timeout.

Tokens: {key} (required), {summary} and {type}; any other text, such as feature/, is kept as written.

{key} keeps Jira's spelling of the issue key; {summary} and {type} become lowercase words joined with hyphens.

Names are capped at 60 characters; only the summary and type are shortened.

A preview of the name appears under the field while you type.

JirAI finds the current issue from the key in the branch name, so a template without {key} is refused.

After creating a branch

What JirAI does with the issue once the branch exists:

• Ask to move the issue to In Progress (default): a notification offers the move.

• Move the issue to In Progress: JirAI moves the issue without asking. This applies to any issue you branch from, including a colleague's.

• Do nothing: the issue keeps its status.

The first time in each project, a notification asks which In Progress status to use, and JirAI remembers your choice.

Issues that are already in progress or done are left as they are.

If the move needs fields filled in, the notification offers to open the issue instead.

Forget remembered In Progress targets now

Clears the In Progress status JirAI remembers for each project, so it asks again.

This link acts at once, without Apply.

Start commit messages with the current issue key

Selected by default.

An empty commit message starts with the key of the current branch's issue, for example DEMO-42.

It works with changelists only, not with the Git staging area, and never replaces a draft or a Git commit template.

See Create a branch from an issue, The current issue in the status bar and Issue key in commit messages.

Metrics

Settings | Tools | JirAI | Metrics

When a space has more than 10,000 work items, JirAI loads a sample of 10,000:

Keep the newest work items (recent weeks stay exact)

The default. Recent weeks are complete, and the oldest weeks under-count.

Keep the oldest work items (long-running work stays visible)

Long-running work stays in the sample, and recent weeks under-count.

The change applies the next time a space tab loads or refreshes.

See Large spaces.

House Standard

Settings | Tools | JirAI | House Standard

Rules that AI assistants are told about when they validate a draft issue, stored for the Jira site you are signed in to.

Project

The project key, or * for any project.

Issue type

The issue type, or * for any type.

Rule

The kind of rule: FIELD_SET, DESCRIPTION_HEADING or FIELD_MATCHES.

Target

The field name, or the heading text for DESCRIPTION_HEADING.

Pattern

A regular expression; used only by FIELD_MATCHES.

Note

Optional. Your own explanation, which the assistant receives instead of the generated message.

See Define a house standard.

Related IDE settings

Settings | Tools | MCP Server

Turns on the IDE's MCP server, which the JirAI agent tools need. See Turn on the agent tools.

Settings | Appearance & Behavior | System Settings | HTTP Proxy

The proxy JirAI uses. See Use JirAI behind a corporate proxy.

Settings | Appearance & Behavior | Notifications

How JirAI notifications are shown.

JirAI has the notification groups Jira issue delete, Jira attachments, JirAI doc push, Jira create, Jira description drafts, JirAI agent tools and JirAI branches.

Keyboard shortcuts

JirAI actions such as New Issue, Space Summary, Push to Jira and Open Current Jira Issue have no default shortcut.

Run them with Find Action (Ctrl+Shift+A, macOS: ⌘ ⇧ A), or assign shortcuts in Settings | Keymap.

New Issue and Space Summary become available once the JirAI tool window has opened in the project and shows you signed in.