Jira - Veryfront

At a glance

Availability: Enabled by default.
Authentication: OAuth 2.0.
Connection: A user authorizes the connection in the provider’s consent screen.
Scopes: read:jira-work, write:jira-work, read:jira-user, offline_access.

Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

Variable	Required	Description
`ATLASSIAN_CLIENT_ID`	Yes	Atlassian OAuth 2.0 Client ID (from your app) Docs.
`ATLASSIAN_CLIENT_SECRET`	Yes	Atlassian OAuth 2.0 Client Secret Docs.
`JIRA_CLOUD_ID`	No	Optional Atlassian site ID; required when the user can access multiple Jira sites Docs.

Tools

Tool	Access	Description
List Atlassian Sites `jira__list_sites`	Read	List Atlassian cloud sites/resources the OAuth token can access; use the returned id as cloudId for Jira and Confluence tools
List Projects `jira__list_projects`	Read	List all accessible Jira projects
Get Project `jira__get_project`	Read	Get detailed information about a Jira project
Search Issues `jira__search_issues`	Read	Search Jira issues using JQL (Jira Query Language)
Get Issue `jira__get_issue`	Read	Get detailed information about a specific Jira issue
Create Issue `jira__create_issue`	Write	Create a new Jira issue in a project
Update Issue `jira__update_issue`	Write	Update an existing Jira issue (status, fields, etc.)
List Comments `jira__list_comments`	Read	List comments on a Jira issue
Add Comment `jira__add_comment`	Write	Add a comment to a Jira issue
Get Transitions `jira__get_transitions`	Read	List available workflow transitions for a Jira issue
Transition Issue `jira__transition_issue`	Write	Move a Jira issue to a new workflow status. First call get_transitions to get valid transition IDs, then pass the ID here.
Search Users `jira__search_users`	Read	Search Jira users by name or email to find the accountId needed for assigning issues

Verify the connection

Call a read tool such as jira__list_sites with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.