Transitioning From v1 to v2

Introduction

After 3 years in the making, we are pleased to announce the release of CueDB v2. We have worked tirelessly to address feedback, implement new features, and improve the overall user experience in this new version.

We understand that change can be daunting, and transitions can be challenging. Therefore, we have put together this guide to help you get started in v2.

Want to use the Legacy App?

We understand that some of our users may be in the middle of important projects and don't have time for a change right now. To ensure your work is not disrupted, v1 will remain accessible during this transition period.

You can continue to use v1 exactly as you're used to by visiting legacy.cuedb.com or by clicking on the "Use the Legacy Version of CueDB" link on the login screen. However, please be aware that this access is temporary, lasting a few months starting from June 2023, after which v1 will be discontinued.

It's important to note that data will not be synced between v1 and v2 after release (June 3 2023), so any changes made in one version will not reflect in the other. The good news is that we now have a powerful Excel Import Feature in v2, so if you want to transfer data after this point, you can export a cue log with all fields from v1 and import it into a new project in v2. The most essential cue data from the Cue Overview will be included.

We encourage all users to start familiarizing themselves with v2 at their earliest convenience, to enjoy the new, enhanced features and improvements we've made. If you're interested to learn more you can visit our changelog.

Important changes

Our main objective has been to keep the essence of all features from v1, while enhancing functionality, improving user experience, and boosting productivity. While we’ve striven to retain every feature from v1, a few changes and compromises have been made.

How we doin'

The "How we doin'" module no longer graces the Dashboard. We realized its utility was outweighed by the resource-heavy demands and under-utilization by many users. However, it may stage a comeback in the future, redesigned and optimized. You can still view individual member stats and progress if you hover a "member avatar" in the column header of the Cue Overview.

Dark mode

The new app comes in dark mode. A lighter version is under development and will be available soon.

Key commands

Rest assured, the key commands you're accustomed to are on their way back. We're committed to reintegrating them promptly.

Global user presets

We've streamlined the preset management in v2 by shifting from global user presets to project-based presets. This change was made to prevent any confusion CueDB might have if you try to save a global preset for projects with different custom fields.

In v2, it's a breeze to handle custom fields and presets. If you want to use the same presets across different projects, it's as simple as importing them under "Project Settings > Import". In addition, when you duplicate a project, all presets are carried over.

Remember, when duplicating a project, everyone's personal presets (that are only visible to each member) will be included. However, if you import presets from another project, only the personal presets that belong to you will be transferred. This design is to safeguard against unintentional overwrites of others' personal presets.

Project-based statuses

With v2, we have shifted from team-based statuses to project-based statuses, giving you limitless status additions and enhanced customization. Just like presets, statuses are included when you duplicate a project and can also be imported from another project under "Project Settings > Import".

New project role requirement

CueDB v2 now requires a role (composer, music editor, orchestrator etc) to be assigned to each project member. In case a project member wasn't given a specific role in v1, they will default to the 'viewer' role in v2. If you or your collaborators encounter any access issues, adjusting member permissions might be needed.

Only one owner of a project

Each project in v2 can only have one owner, a move intended to simplify project ownership and reduce redundancy. This should also make switching ownership easier.

No longer possible to create multiple teams

Creating multiple teams is no longer available. Those who owned multiple teams can still access them in v2. Just remember to select your primary team under Team Settings.

New stats sidebar

The stats have been repositioned to a sidebar, doing away with the need for constant scrolling. This way, you can view stats and make changes in real-time.