2025-10-01 - Lost app settings after upgrading Timepiece - Time In Status for Jira Data Center to version 6.3.x or 6.4.x

Title

Lost app settings after upgrading “Timepiece - Time In Status for Jira Data Center” to version 6.3.x or 6.4.x

Summary

Some users reported losing their saved settings (Calendars, Param Sets, etc.) for “Timepiece - Time in Status for Jira Data Center” after upgrading the app from an earlier version to version 6.3.x or 6.4.x

The cause of this problem was identified and patched starting with Timepiece 6.5.0.

KB Article Release Date

01 Oct 2025

Affected Products

Timepiece - Time in Status for Jira Data Center

Affected Version(s)

• 6.3.0

• 6.3.1

• 6.4.0

Fixed Version(s)

• 6.5.0 and above

Details

Active Objects database tables were created with incorrect naming in Timepiece versions 6.3.x and 6.4.x, making the data in the original tables inaccessible.

No data was actually lost, but the app was accessing incorrect tables to read/write settings.

Due to custom OSGi instructions in the Maven plugin configuration, Active Objects tables in Timepiece versions 6.3.x and 6.4.x were created with an incorrect hash prefix (AO_4A567D_) instead of the expected prefix (AO_956E29_). This caused any data (calendar settings, report configurations, export history, format settings, and application properties) saved in earlier Timepiece versions to be inaccessible after the upgrade, and new data saved in affected Timepiece versions to be stored in incorrectly named tables.

Fix

The root cause of this problem was identified and fixed in Timepiece 6.5.0

All Timepiece Data Center customers are recommended to upgrade to Timepiece v6.5.0 or above.

What you should do

If you "have NOT used Timepiece v6.3 or v6.4" or you "have used Timepiece v6.3 or v6.4 but have NOT saved any new app settings":

• Simply upgrade directly to version 6.5 or newer. No additional steps required.

If you HAVE used/saved data in Timepiece v6.3 or v6.4 and want to keep that data after upgrading to 6.5 or newer:

You will need to migrate your data before upgrading to v6.5. Follow these steps:

1. Before upgrading Timepiece to v6.5, back up your database.

2. Upgrade Timepiece to version 6.5

3. Migrate your data from the incorrect tables to the correct ones: You need to transfer records from the following source tables to their corresponding target tables. For each setting type, review the records in the source table and transfer the ones you want to keep to the target table.

Support

If you have questions, you can reach the OBSS support team through OBSS Apps Support.

Frequently Asked Questions (FAQ)

I am using Jira Cloud. Do I need to do anything?

• No, this issue only affects Timepiece for Jira Data Center. Timepiece for Jira Cloud users don't need to do anything.

I haven't upgraded Timepiece to version 6.3 or 6.4 yet. What should I do?

• Skip versions 6.3 and 6.4 entirely and upgrade Timepiece directly to version 6.5.0 or later.

I upgraded Timepiece to 6.3 or 6.4 but haven't used the app yet. Do I need to migrate?

• No. If you haven't created/updated any settings (calendar settings, reports settings, format settings) in these versions or you think that any changes made in v6.3 and v6.4 can be ignored, you can upgrade Timepiece directly to 6.5 without migrating any data.

What happens if I upgrade to 6.5.0 without migrating my data?

• Your new settings saved on Timepiece versions 6.3 and 6.4 (calendar configurations, report settings, and format settings) will not be available in version 6.5.0, as they remain in the old tables. Any data created in Timepiece 6.2.x or earlier will still be available.

Do other OBSS apps have this issue?

• No, this issue is specific to Timepiece - Time in Status for Jira Data Center versions 6.3 and 6.4.