Check Request #19 - Payload upgrade issue should be linked to component fix about bug-clerk HOT 4 CLOSED

@baranowb I've implemented the first part of this check (this, but before pushing it, I want to double check with you that the behavior is proper.

On the current payload, BZ1218663 has no component upgrade associated with. This triggers an alert from Bugclerk. On the contrary BZ1218663 has a indeed a component upgrade, and will therefore not trigger the checks...

Sounds good for you ?

from bug-clerk.

OK, right now, there is a drawback, that I think need to be fixed to release those checks as "ERROR" and no just WARNING. Indeed, the current implies that the dependency of any issue needs to be loaded during the initial import or otherwise, from Bugclerk point of view "it does not exist".

So if the filter used to retrieve, for instance, payload tracker issue, does not also load its dependency, the current checks will give back false+ and/or false-.

For now I'm going to release those checks as there are, as warning. Indeed they are usable, if the filter used for the important is well crafted.

from bug-clerk.

Issue #38 has been opened to document the need for enhancement on this front.

from bug-clerk.

Implemented (see commit 9fab31a) and will be released with 0.9.0

from bug-clerk.