Jira Cloud

Required Jira Permissions

Paradime authenticates to Jira with an Atlassian API token (Jira Cloud) or a Personal Access Token (Jira Data Center). These tokens carry no scopes of their own — they act as the user who created them, so the token owner’s Jira account needs the project permissions for the actions you want DinoAI to perform:

DinoAI action	Jira project permission
Fetch, list, and search issues	Browse Projects
Create issues	Create Issues
Update summary, description, labels, priority	Edit Issues
Change issue status	Transition Issues
Change assignee	Assign Issues
Add comments	Add Comments

Tip: Connect Jira with a dedicated service account whose project permissions cover exactly the actions above. Since API tokens are unscoped, the account’s permissions are the real boundary of what DinoAI can do in Jira.

Read-only usage (fetching and searching issues) only requires Browse Projects. If your organization uses Atlassian’s newer scoped API tokens, the equivalent scopes are read:jira-work for reading and write:jira-work for creating, updating, and commenting.

For Jira Data Center users, see Connecting Jira Data Center to Paradime for setup instructions specific to your environment.

Once connected, DinoAI will be able to access Jira on your behalf using the Confluence Tool.

Jira Cloud

You will need an Atlassian API key to connect Jira Cloud. See the table below for instructions on where to find each required field.

Field	Description	Where to find it
Jira Domain	The subdomain of your Jira Cloud account	Your Jira URL, e.g. `https://your-org.atlassian.net`
Email Address	The email address associated with your Atlassian account	Your Atlassian account profile
API Key	A personal API key to authenticate requests	Go to id.atlassian.com → Security → Create and manage API tokens

Once all fields are filled in, click Connect to complete the connection.

​Required Jira Permissions

​Jira Cloud

Required Jira Permissions