• Jira features table
• Jira Migration Notes
• Learnings
• Users and permissions

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.)

• JIRA migrators implemented in other PM tools

  • YouTrack

    • https://www.jetbrains.com/help/youtrack/server/migrate-from-jira-to-youtrack.html

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

    • Nice entities mapping table: https://www.jetbrains.com/help/youtrack/server/new-import-from-jira.html#import-details-jira

  • ClickUp

    • https://help.clickup.com/hc/en-us/articles/6310954639255-import-from-jira

      • New importer which uses backups as a data source

    • https://help.clickup.com/hc/en-us/articles/12224657564695-import-from-jira-legacy

      • Legacy importer uses rest API

• JIRA DATA CENTER

  • End of life details: https://www.atlassian.com/licensing/data-center-end-of-life#data-center-eol-general-questions

  • End of support details: https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html

  • REST API DOCS

    • Last version: https://developer.atlassian.com/server/jira/platform/rest/latest

    • Previous versions list: https://developer.atlassian.com/server/jira/platform/rest/v11003/intro/#previous-versions

    • How to create and use a persona access token: https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html

    • Folder with old REST API API versions by build number: https://docs.atlassian.com/software/jira/docs/api/REST/

      • to find a build number serverInfo endpoint can be used: https://docs.atlassian.com/software/jira/docs/api/REST/1000.300.0/#api/2/serverInfo-getServerInfo

  • REQUEST RATE limiting can be disabled

  • LOGS

    • Useful log files: https://confluence.atlassian.com/jirakb/useful-log-files-in-jira-1027120387.html

    • For example access logs can be useful to see what requests other PM tools sent to get data from JIRA instance.

  • DATABASE SCHEMA

    • https://developer.atlassian.com/server/jira/platform/database-schema/

  • VERSION RELEASE NOTES

    • https://confluence.atlassian.com/jirasoftware/jira-software-release-notes-776821069.html

• JIRA CLOUD

  • REST API DOCS

    • v2: https://developer.atlassian.com/cloud/jira/platform/rest/v2/

    • v3: https://developer.atlassian.com/cloud/jira/platform/rest/v3/

  • USERS sync

    • through REST API potential bummers

      • email can be hidden due to Privacy Policy

        • https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-users-search-get

        • https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-users/#api-rest-api-2-users-search-get

      • if inactive/deleted user has no Atlasian account it will not be returned by the API

        • https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-users-search-get

        • https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-users/#api-rest-api-2-users-search-get

    • through SCIM API

      • https://developer.atlassian.com/cloud/admin/user-provisioning/rest/intro/#about

  • REQUEST RATE limiting must taking into consideration to get data through APIs