Skip to end of banner
Go to start of banner

Hybrid Planning Poker Server EOL - March 31st, 2022

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

A “hybrid” version of Planning Poker for Jira Server / DC that connected to cloud services of Planning Poker app will be decommissioned on . Please follow instructions provided below to migrate to the “on-premise” version of Planning Poker for Jira Server.

In case if you do not migrate by Planning Poker will stop working afterwards - error pages will be returned.

Instructions

  1. In your Jira Server / DC instance:

    1. Navigate to Jira administration → Manage apps

    2. Load Manage apps screen

    3. Look up for Planning Poker for JIRA app - an app update should be available

    4. Hit Update button

    5. Note: a valid Jira Server/DC license is required to update the apps

    6. Wait for the app to be updated

  2. Open Planning Poker app:

    1. Using Planning Poker link either from the Jira’s top navigation menu or from project’s left navigation panel

    2. Note: your existing Planning Poker’s games may be unavailable at this moment. No panic, they will be brought back in the next steps!

    3. Locate Migrate button - either on Planning Poker’s welcome screen or on the games list (dashboard) page:

    4. Hit Migrate button and wait for the migration process to complete

  3. You are done. At this stage Planning Poker stores all games and estimation information inside your Jira Server / DC instance, and doesn’t connect to the external services.

FAQ

 1. What is a “hybrid” version of Planning Poker for Jira Server / DC?

The initial version of Planning Poker app was created for Jira Cloud. As it was getting more popular we got requests to make it available for Jira Server / DC. There is not much in common between Jira Server / DC and Cloud, so making app available for another deployment type would mean re-writing it from the scratch.

And that’s when the “hybrid” version of Planning Poker for Jira Server / DC was released. That app connected to cloud services of Planning Poker as the storage and processing engine. The user interacted with Cloud version of the app injected into Jira Server / DC through iframe.

Some time later an “on-premise” version of Planning Poker was released that didn’t rely on external services and stored all data inside Jira Server / DC database.

A migration mechanism was added so customers could easily switch to “on-premise” version and keep using Planning Poker.

 2. Why do you decommission a “hybrid” version now?

As we keep adding more features to Planning Poker for Cloud and Server / DC, we can’t longer maintain a compatibility between “hybrid” and Cloud version. That dependency significantly slows us down and increases chances of introducing bugs in both versions of the software.

We have recently migrated Planning Poker for Jira Cloud from Digital Ocean provider to GCP (Google Cloud Platform) - see List of changes in Data Security and Privacy Statement: v1 to v2. And we are going to shut down the “hybrid” version of the app on that will unblock decommissioning of service in Digital Ocean and will also reduce our operational costs.

 3. I do not have a valid Jira license. What should I do?

You should buy or re-new a Jira Server license for Jira first, and then purchase / re-new Planning Poker license.

Open questions:

  1. Do we want to give them “free” license? Can we do that?

  2. Will they be able to update app if Jira license expired, or valid Jira license is must have?

  • No labels
Error formatting macro: appfire-confluence-analytics: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null