Wammu Mantis bug tracker link broken?

[Michal Čihař]

https://bugs.launchpad.net/ubuntu/+source/wammu/+bug/224344 says:

Wammu Mantis bug #468 appears not to exist. Check that the bug number is correct.

but clicking on the link shows bug properly. Is there something special what has to be configured in Mantis side to make this link work?

[Graham Binns (gmb)]

Converting this to a question since it's not necessarily a bug with Launchpad, though it needs investigating.

[Gavin Panella (allenap)]

Bug 468 is not appearing in the CSV download that our robot fetches. The robot has an alternative mode to scrape the UI, and this mode can successfully download the status of bug 468. However, because the CSV is downloaded okay, the alternative mode is not used (many Mantis trackers disable CSV downloads or simply seem to be broken, which was the rationale for creating the scraping mode).

From my browser, I managed to get bug 468 to appear in the CSV download by mucking around with the filter settings. However, I don't really understand what I did! Ultimately, it looks like we're missing a parameter or sending an incorrect parameter when setting up the filter before downloading the CSV.

In short, this looks like a bug in our robot.

[Gavin Panella (allenap)]

Fixing this bug looks like an exercise in pain. It /might/ be simple, but figuring out Mantis's filter incantations and subtle dances (especially from the perspective of a non-human client) has caused me such consternation in the past that I'm reluctant to invest time here, lest it become a black hole.

In any case, both methods that we use for querying Mantis remotely - CSV and page-scraping - are suboptimal, so it's probably better to invest time in creating a plug-in for Mantis that would allow efficient and reliable status synchronization (and - optionally - bidirectional comment sync).