• Go through all open Jira tickets, flagged with "top_flaky_test" on dev, 6.9, 6.8, 6.5
• Check whether the test function is still flaky (by inspecting relevant Grafana dashboards or other appropriate means)

=> If the test is still flaky, add a respective comment to document that it is flaky and unfixed.

=> If the test isn't flaky anymore, add a comment (if possible to) document when the flakiness has stopped.

• if it's blacklisted, push an unblacklisting patch that closes the ticket.
• If it isn't blacklisted, close the ticket.

Let's start with the oldest tests affecting dev.
As for missing data in week 27, it can be assumed that a test that hasn't been flaky for 4 weeks before week 27 hasn't become flaky again in week 27.

We only create tickets for dev. The "missing data" may happen is all top flaky tests from previous week were still in top 5 - we do not create duplicates of tickets.