ussnorway: to be blunt I already picked an accurate name; its a bug and it is about BG3
The name may not be wrong, but it's not descriptive enough to filter on.
Suppose that user Joe also plays Baldur's Gate 3, and encounters a crash-to-desktop when completing a particular side-quest, but only on the latest patch. As a good beta tester, he wants to report the problem if it's not already known, but also would rather not write up a thorough and proper bug report[1] if someone else has already done so. Good bug reports take time to assemble. (Instead, he should add a note on the existing report that he sees it, and remark on any significant differences between his crash and the reported one.) Thus, Joe heads off to the GOG Baldur's Gate forums to check to see if someone else has already reported his problem. (We'll assume he can find your posts here even though this forum is for Baldur's Gate 1 and Baldur's Gate 2, and GOG has a separate forum for Baldur's Gate 3.) Joe finds you have not one or two, but more than a dozen bug reports. Then he notices they're all titled "Bug Bg3". Are any of them about his particular crash? He'll need to open and read all of them to find out. If instead you had made full use of the subject line, he could quickly filter out reports that are obviously different from his crash bug. It's useful if you report a bug where the game refuses to recognize a quest as done, but that's not a crash bug, so he doesn't even need to read a thread titled "Bug BG3: Storyline does not advance to Chapter 3".
[1] With steps to reproduce, links to any error logs the game produced, and preferably a savegame that can be loaded to put the player in the right place to immediately trigger the crash.