Jira Data Center End of Life - Hub Integration

What is Jira Data Center End of Life?

Atlassian has announced that support for Jira Server and Data Center on-premises installations will be discontinued on February 15, 2024. After this date, Atlassian will only offer Jira Cloud as their supported solution.

Some customers may continue to use their on-premises installations with extended support, but all on-premises support will be completely discontinued from March 28, 2029.

What does this mean for teams using Jira on-premises?

Teams currently using Jira Server or Data Center for managing their work must migrate their Jira instance data to Jira Cloud before support ends. Atlassian provides migration tools and documentation to assist with this process. While Atlassian's migration tools ensure that Jira Cloud is functionally equivalent after migration, the underlying data identifiers change, which can impact integrated tools.

Key data identified changing during migration:

• Work item IDs (Issue API IDs) will change

• Field IDs will be modified

• Type IDs will be reassigned

• Project IDs will be reassigned

• Custom field mappings may need reconfiguration

• Option schema may be modified

• Project configurations may need adjustments

How does Jira migration impact Hub's integration?

Hub stores repository information and metadata to access and sync data with Jira. This includes but not limited to:

• Repository configuration and connection details

• Jira schema data (projects, issue types, fields, workflows)

• Work item mappings and relationships

• API identifiers for synced artifacts

When Jira migrates from on-premises to Cloud, Hub may encounter the following issues if they are not addressed prior to enabling the updated integration:

1. Repository Configuration Becomes Invalid: The repository has a new URL and will have a new schema for its data.

2. Schema Data Conflicts: Hub's cached Jira schema (custom fields, workflows, issue types) no longer aligns with the Cloud instance's structure.

3. ID Mismatches Occur: All work item API IDs, field IDs, and type IDs change during migration. Hub's stored references no longer match the Cloud instance.

4. Duplicate Work Items Created: Because API IDs have changed, Hub cannot recognize existing work items and treats migrated items as "new," potentially creating duplicate pairs and sync relationships.

Can I just update the repository URL in Hub after Jira migration?

No, simply updating the repository URL is not sufficient. While this changes where Hub connects, it does not resolve the fundamental data mismatch issues:

• Existing work item mappings will break

• Schema data will be inconsistent

• Duplicate work items will likely be created due to wrong API IDs

• Synchronization may fail or produce unexpected results

• Historical traceability may be lost

How can Hub continue working with Jira Cloud after migration?

Hub requires a comprehensive data migration to align with the Jira Cloud instance after migration. This involves:

1. Schema Data Migration: Updating Hub's stored Jira schema to match the new Cloud structure (projects, issue types, fields, workflows, etc.)

2. Artifact Data Migration: Remapping all stored work items and relationships to use the new Cloud API identifiers

3. Mapping Preservation: Maintaining existing relationships between Hub artifacts and Jira items despite ID changes

4. Configuration Updates: Updating repository settings, authentication, and connection details

5. Edge Case Handling: Addressing custom configurations, complex field mappings, and unique integration scenarios

Can I perform this migration myself?

Due to the complexity of the data migration and the numerous edge cases involved, we strongly recommend engaging Planview’s Professional Services team for this migration.

Why Professional Services is recommended:

• Expertise: Years of experience with Hub-Jira data migrations

• Specialized Tools: Custom migration utilities designed for this specific scenario

• Edge Case Handling: Ability to address complex configurations and unexpected issues

• Data Integrity: Ensures traceability and relationships are preserved

• Risk Mitigation: Reduces the risk of data loss or duplication

• Time Efficiency: Faster completion with fewer issues

How do I request Professional Services assistance?

To engage our Professional Services team for Jira migration support:

1. Contact your Care Team: Reach out to your designated customer success or support contact or file a support ticket here: customer care.

2. Request Data Migration Services: Specifically mention "Jira on-premises to Cloud migration for Hub integration"

3. Provide Details: Share information about your Jira environment and migration timeline

4. Schedule Consultation: Work with Professional Services to plan the migration

Contact Professional Services: Please reach out to your Care team to be connected with Planview’s Professional Services specialists who can assess your specific situation and provide a migration plan.

What information should I prepare before contacting Professional Services?

Having the following information ready will help expedite the process:

• Current Jira Server/Data Center version

• Planned Jira Cloud migration timeline

• Number of projects and work items in Jira

• Current Hub versions if using on-premise Hub installation

• Hub repositories currently integrated with Jira

• Custom field configurations and workflows

• Any custom integrations or scripts using the Hub-Jira connection

• Business criticality and timeline constraints

What happens if I don't migrate my Hub data?

If you migrate Jira to Cloud but do not migrate Hub's integration data:

• ❌ Existing work item mappings will be broken

• ❌ Duplicate work items will be created

• ❌ Historical traceability will be lost

• ❌ Synchronization will fail or produce incorrect results

• ❌ You may need to manually clean up duplicate data

• ❌ Significant effort will be required to restore proper integration

How long does the Hub data migration take?

Migration duration varies based on:

• Size of your Jira instance (number of projects, issues, fields)

• Complexity of your Hub-Jira integration

• Custom configurations and edge cases

• Coordination between teams

Our Professional Services team will provide a detailed timeline estimate during the initial consultation based on your specific environment.

Please contact your Care team at the Care Portal for assistance with Jira Data Center end of life planning and Hub migration services.