Back in early October, we asked a question about automatic upgrades of Connect-on-Forge apps that adopt Forge manifest.
At the time, we had just finished converting our first Connect app from atlassian-connect.json → manifest.yml, and after successfully testing in dev/staging and then deploying to the production environment, we waited for our main production instance that has the Connect-only version installed from the Marketplace to be automatically upgraded.
It is very important to us to see and “feel” what an automated Connect → Forge upgrade experience is like for customers using our own instance before continuing to move the remainder of our app portfolio to Connect-on-Forge. So we paused all further Forge migration work, pending the outcome of this one automated upgrade.
It was at this time that we became aware that Atlassian had temporarily paused Connect to Forge migrations a few weeks earlier on 23 September. Although this was announced via a Changelog entry, judging by the comments both on CDAC and the related ticket in JAC, it seemed that we weren’t the only ones to be learning about this for the first time.
Shortly after, on 10 October, a estimated date for when automated upgrades would resume was given: 17 November. This was later revised to 24 November.
True to their word, Atlassian did resume automated upgrades on that date, however it was noted that there would be a gradual ramp up, presumably to avoid overwhelming both the app’s /install endpoint and Atlassian’s infrastructure.
Upgrades started to trickle into the Developer console, but a very slow pace….one or two upgrades per day. The app we migrated is our least popular (the reason why we chose to migrate that one first), so the total number of upgrades is expected to be relatively low. Even still, the rate at which they are appearing in our Developer console suggests that it could be quite some time before the backlog of installs to be upgraded is cleared.
More concerning though, is that the majority of upgrades so far appear to be for expired evaluations, some as far back as 2020 (5 years ago). There seems to be no priority given to upgrading active, paid customers first; and it is unclear why an expired trial from 5 years ago even needs to be upgraded at all?
So to recap:
- Automatic upgrades were paused for a total period of two months (23 September - 24 November)
- On resumption, they appear to be happening at a snail’s pace (1-2 upgrades per day in our case)
- There is no ordering or filtering applied to the backlog, so “useless” upgrades for evaluations that are never likely to be touched again are happening before paid/active customers.
I have been trying to get a straight answer from the team that delivered ECO-1077 on when the backlog is expected to be cleared, but so far I have been unsuccessful in doing so.
So I’m posting here to increase visibility in the hope that we can finally get back to the remainder of our Connect → Forge migrations (which ironically was driven by Atlassian’s desire to get everyone onto Forge in the first place).
(cc: @FeiyangYe, @rmassaioli )