Unhelpful "There was 1 error" for unrecognized bug tracker

[Matthew Paul Thomas]

1. Go to any bug report that is filed against a project that uses an external bug tracker, but that does not currently have a bug watch.
2. Click the triangle next to the project name.
3. In the Remote Watch URL field, enter an URL that doesn't match the registered bug tracker, and choose "Save Changes".

What happens:
* An error message appears: "There is 1 error in the data you entered. Please fix it and try again."
* No other hint as to what is wrong or how you should fix it.

What should happen: An explanation that it is the bug tracker URL that wasn't recognized.

[Neal McBurnett (nealmcb)]

This should not be ignored for a year as "low" importance.

I just spent my time dutifully trying to help people by using on of Launchpad's key features (integrating different bug tracking systems), only to be repeated and mysteriously rejected because of this bug.

I was trying to help with this bug:

https://bugs.launchpad.net/hamster-applet/+bug/926481/+editstatus

which should now point to

https://github.com/projecthamster/hamster/issues/24

with the update text:

Hamster is now using github to track bugs.
This issue is now also fixed upstream:
https://github.com/projecthamster/hamster/issues/24

Not only that, but it throws away the text I entered after giving me the unhelpful message.

 It is discouraging!

Please fix it :)

[Neal McBurnett (nealmcb)]

In the meantime, what is the best workaround for this bug, so affected bugs for upstream projects in launchpad can correctly report upstream progress, or at least not incorrectly report it?

[jazzynico (jazzynico)]

Just ran into the same issue today. So sad GitHub issues can't be linked in LP's reports.