Apparently FoD imposes a maximum length for the vulnerability bugLink field, causing FoD HTTP 500 errors when the bugLink field exceeds the maximum length.
As such, the functionality for storing the bug link for submitted issues in the FoD bugLink field currently does not work reliably. The current default configuration files therefore store issue link and id in FoD vulnerability comments instead.
This issue is under investigation by the FoD team. Once resolved, this issue can be closed. It still needs to be decided though what should be the default settings in the default configuration files; store the bug link in the FoD bugLink field or in vulnerability comments?
Apparently FoD imposes a maximum length for the vulnerability bugLink field, causing FoD HTTP 500 errors when the bugLink field exceeds the maximum length.
As such, the functionality for storing the bug link for submitted issues in the FoD bugLink field currently does not work reliably. The current default configuration files therefore store issue link and id in FoD vulnerability comments instead.
This issue is under investigation by the FoD team. Once resolved, this issue can be closed. It still needs to be decided though what should be the default settings in the default configuration files; store the bug link in the FoD bugLink field or in vulnerability comments?