Jira Cloud

The Jira Cloud package uses your Atlassian account email and API token. It supports issue search, project listing, comments, transitions, creation, updates, and assignment.

Connect the account

Enter the Jira Cloud site URL, Atlassian account email, and API token. Scoped tokens are routed through Atlassian’s cloud API path; legacy unscoped tokens use the configured site URL. The connector detects the route and Cloud ID automatically.

Use a service or user account whose Jira permissions match the intended work. Pneum.ai cannot grant project permissions the account does not already have.

Add project keys

The connector allowlist contains Jira project keys such as ENG or OPS, not display names. Every issue key is checked by its project prefix. JQL searches are automatically wrapped to remain inside the allowed projects.

Test one allowed project and a known disallowed project before enabling writes.

Select tools

Read tools include JQL search, issue details, projects, comments, and available transitions. Write tools include create, update, comment, assign, and transition.

Enable writes only for workflows the connected account is authorized to perform. A transition tool can use only transitions currently offered by Jira for that issue.

Write safely

Keep issue creation, assignment, and workflow transitions behind approval. Review project key, issue key, assignee identity, field values, and transition name.

For bulk work, ask the agent to produce a proposed list before executing changes one by one or under a deliberately bounded persistent grant.

Troubleshoot

• Authentication failure: create a current API token and confirm the account email.
• No projects: confirm the token account can browse them and their keys are allowlisted.
• JQL returns less than expected: remember the connector adds the project boundary.
• Transition rejected: list the issue’s current transitions and choose one of those exact values.