TOPdesk for Jira is migrating to Atlassian’s new Forge platform. The migration will be finished before Connect (the current platform) is end of support. The new version will be fully compatible if the platform allows.
Roadmap
|
|
Expected |
|
|---|---|---|
|
Connect on Forge version |
This version is the first step in the migration. This is the app on the new platform with the current platform modules embedded. This is a necessary step in order to be able to migrate configuration and data to the new platform |
|
|
Full Forge, with legacy support |
We are fully migrated to the new platform. This means you can finish migrating TOPdesk action sequences to point to the new platform. At the same time we will still support the old configuration by keeping the legacy app up and running. |
|
|
Forge only |
The legacy support will be removed. This is a hard deadline as call from our legacy platform will be denied by Atlassian. |
Q&A
Q: What is the current status of your Connect-to-Forge migration
Well underway, specification is almost done, implementation starting
Q: Whether a Forge version is already available
Not yet… but stay tuned and check the roadmap
Q: Your roadmap and expected timeline for the migration (if applicable)
Current ETA is well before the end of the year.
Q: Any planned changes to functionality, permissions, or pricing as part of the migration
The Forge app is currently being specced and will use Forge features to be a better app than it’s Connect predecessor. That said, we will strive for 100% backwards compatibility.
Q: Whether existing customers will need to perform any actions during the transition
There will be at least an explicit upgrade confirmation, at minimum including accepting the Forge scopes.
Q: Any known limitations or dependencies related to the Forge version
Not that we see now.