Overview

Export task breakdowns from Projan plans directly to Jira as Epics, Stories, and Tasks with dependency linking.

Prerequisites

• Jira Cloud instance (not Server or Data Center)
• Project admin access for the target project
• Projan team admin or individual account

Setup Steps

1. Go to Settings > Integrations > Jira
2. Click “Connect Jira”
3. Authorize via Atlassian’s OAuth consent screen
4. Select your Jira site if you have multiple
5. Grant the requested permissions

Permissions Requested

Scope	Purpose	Access Level
read:jira-work	Read projects, issues, boards	Read
write:jira-work	Create and update issues	Write
read:jira-user	Look up assignable users	Read
manage:jira-project	Access project configuration	Read
manage:jira-configuration	Read issue types and workflows	Read
offline_access	Refresh tokens without re-auth	System

What Data is Accessed

• Project names and keys
• Issue types and workflow configurations
• Existing issues (for dependency linking)
• User accounts (for assignment suggestions)

Data Storage

• Encrypted access and refresh tokens
• Jira site URL and cloud ID
• Installer account ID

Tokens auto-refresh - no re-authentication needed unless you revoke access from Atlassian.

Disconnecting

Go to Settings > Integrations > Jira > Disconnect.

This immediately purges all stored tokens. Previously exported issues remain in Jira unaffected.

Troubleshooting

“No projects found”

• Verify you have project admin access for at least one project
• Ensure the connected account has the correct Jira permissions

Token expired

• Tokens should auto-refresh. If issues persist, disconnect and reconnect

Missing issue types

• Ensure the target project uses a standard issue type scheme
• Custom issue types are not automatically mapped

Export fails with “Permission denied”

• The connected Jira account must have “Create Issues” permission in the target project