Jira Sync Notes

Existing work:
https://github.com/dotnetfactory/openproject-jira-importer 
https://github.com/netresearch/jira-to-openproject  (probably AI-generated)
https://github.com/LLR1/universal-wp-migration

Competition

https://www.jetbrains.com/help/youtrack/server/new-import-from-jira.html

Authentication & Authorization

• Supported authentication mechanisms (API token, OAuth, Basic Auth)

• Rights and role concepts in both systems

• Secure storage of credentials/tokens

Data Model Mapping

• Entities to be synchronized (e.g., projects, issues, comments, attachments, users)

• Field mappings (custom fields, required fields, status, priorities)

• Handling of fields/add-ons that cannot be mapped

• Scope of sync (Cost-Reports?)

• Handling of deleted elements

Synchronization Direction & Frequency

• One-way synchronization (only Jira → OpenProject)

• Initial migration vs. ongoing synchronization

System Compatibility

• Support for different Jira and OpenProject versions (SaaS/On-Premise)

• API compatibility and limits

Error Handling & Logging

• Handling of synchronization errors (e.g., missing fields/users)

• Logging and monitoring of synchronization processes

• Error notifications

• Ability to track individual changes (history)

• Triggering notifications in OpenProject (or suppressing them)

Performance & Scalability

• Synchronization of large data volumes

• Performance requirements

• API rate limits

Configurability

• Selection of projects to be synchronized

• Filter and mapping rules

Testability

• Test environments and test data

• Options for dry runs and rollbacks

• Reference customers with real data

Legal Considerations

• API usage

• Compliance with data protection regulations (GDPR, etc.)