Note that using the Issue Tracker you can ...
Look up a particular issue e.g.
https://4js.com/en/support/issue/?id=FGL-3979See all outstanding issues e.g.
https://4js.com/en/support/issue/?id=&product=FGL&stat=OPENLook up issues with a keyword(s) e.g.
https://4js.com/en/support/issue/?id=&product=FGL&stat=&words=fgldbsch&Search=SearchIssues fixed in a certain release e.g.
https://4js.com/en/support/issue/?id=&product=FGL&stat=CLOSED&fixed_in=2.50Issues fixed between releases e.g.
https://4js.com/en/support/issue/?id=&product=FGL&stat=CLOSED&fixed_in=2.50.10-2.50.16&words=&Search=Search... just be entering different values in the Issue Tracker fields.
When reporting an issue, you will hopefully be given an issue number which you can use to track the progress of the issue, and to use as reference in any follow up. I would recommend checking the entry in the Issue Tracker once you are given the number to check the description matches your understanding of the issue. (it also helps check that the issue has been marked as public so it appears in the Issue Tracker, default value is private and occasionally this step gets missed)
It should also be noted that internally the issues database has recently switched from Bugzilla to JIRA. Bugzilla reference numbers were upto five digits and colloquially prefixed with Bz e.g. Bz12345. JIRA numbers are smaller and have a product prefix e.g. FGL-1234, GDC-1234, GST-1234 etc. Both sets of numbers should be searchable in the Issue Tracker. Without a prefix for old numbers
https://4js.com/en/support/issue/?id=12345, the same bug with a prefix for newer numbers
https://4js.com/en/support/issue/?id=GDC-02105, so don't worry if you only have an old style Bz issue number, you should still be able to find it.
Reuben