...
...
...
...
| Info |
|---|
Who is impacted by this announcement?
|
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.
| Table of Contents |
|---|
| Note |
|---|
In case if you do not migrate by Planning Poker will stop working afterwards - error pages will be returned. |
...
Instructions
In your Jira Server / DC instance:
Navigate to Jira administration → Manage apps
Load Manage apps screen
Look up for Planning Poker for JIRA app - an app update should be available
...
Hit Update button
Note: a valid Jira Server/DC license is required to update the apps
...
Wait for the app to be updated
Open Planning Poker app:
Using Planning Poker link either from the Jira’s top navigation menu or from project’s left navigation panel
Note: your existing Planning Poker’s games may be unavailable at this moment. No panic, they will be brought back in the next steps!
Locate Migrate button - either on Planning Poker’s welcome screen or on the games list (dashboard) page:
...
Hit Migrate button and wait for the migration process to complete
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
| Expand | ||
|---|---|---|
| ||
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 almost 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 a “server native” an “on-premise” version of Planning Poker was released that doesn’t didn’t rely on external services and stores stored all data inside Jira Server / DC database. A migration mechanism was added so customers could easily switch to “server native” “on-premise” version and keep using Planning Poker. |
| Expand | ||
|---|---|---|
| ||
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. |
| Expand | ||
|---|---|---|
|
...
|
...
You should buy or re-new a Jira Server license for Jira first, and then purchase / re-new Planning Poker license.
Open questions:
...
Do we want to give them “free” license? Can we do that?
...
|
| Expand | ||
|---|---|---|
| ||
Two options are possible:
|