Details
-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
Up until now, the release webapp has relied on new changelogs appearing on the top of the following page: https://jira.magnolia-cms.com/secure/ManageFilters.jspa?filterView=search
As Jira doesn't provide APIs to browse filters, the bot instead crawls the page.
However, a recent Jira upgrade now orders changelogs by their popularity, which prevents the whole algorithm from running. It appears that the 6.2.13 CL got popular (5 votes), and that it's going to be a the top at the table until people who have starred it unstar it. A Jira admin can't however remove those stars, nor see whom they belong to.
Another problem is that many old CLs (4.5.x, 5.3.x, etc.) fill up the list. If only relevant filters appeared on that page, then we could probably make sure we would always be able to grab the latest changelog.
Solutions:
- Jira Cloud has APIs to browse filters, short-term migration not realistic though
- manually star the latest CL so that it can be found with Jira's API to browse a user's starred filters (cumbersome)
- clean up unused filters, export them & archive them to Google Drive / S3. Write redirects to the new place (requires ongoing work)
- discard Jira altogether, create a manual release task to write the current changelog ID so the release-webapp knows it
(chosen impl. solution)