Overview

Export task breakdowns from Projan plans to Azure DevOps as Epics, Features, User Stories, Tasks, and Bugs, preserving the plan hierarchy with parent-child links. Existing work items can be imported as conversation context.

Prerequisites

• Azure DevOps organisation with a project using the Agile, Scrum, or Basic process
• Work item creation permission in the target project
• Projan team admin or individual account

Setup Steps

1. Go to Settings > Integrations > Azure DevOps
2. Click “Connect Azure DevOps”
3. Sign in with your Microsoft account and authorize the connection
4. Select your organisation and project during export

Permissions Requested

Scope	Purpose	Access Level
vso.work_write	Create and update work items	Write
vso.project	List projects and process templates	Read
vso.wiki_write	Export documents to project wikis	Write

What Data is Accessed

• Organisation and project names
• Work item types and process configuration
• Existing work items (for dependency linking and context import)

Data Storage

• Encrypted access and refresh tokens
• Organisation URL

Tokens auto-refresh - no re-authentication needed unless you revoke access from your Microsoft account.

Disconnecting

Go to Settings > Integrations > Azure DevOps > Disconnect.

Tokens are purged immediately. Previously exported work items remain in Azure DevOps unaffected.

Troubleshooting

“No projects found”

• Check that the connected account is a member of at least one Azure DevOps organisation

Work item types missing

• The available types depend on the project’s process template (Agile, Scrum, Basic, CMMI)

Export fails with “Permission denied”

• The connected account needs “Edit work items in this node” permission in the target area path