Treb Master of the Shiverpeaks
In-game Bug report = Horrible outdated
Treb Master of the Shiverpeaks
It still does exactly what it says on the tin: submits a bug report to anet, to which they will not respond directly. (Plus, unstated, it also includes technical details such as which map shard you are on, location, etc, which make it better for reporting, eg, terrain problems.)
Anyway, both of the things you name probably fit under “terrain” or “dynamic events” in bucket. Just use whatever is closest if you can’t find something exact.
Don’t forget the “blocking progress” checkbox, if it does.
It would probably be better if they oversimplified the pull downs, because ultimately, someone still has to review the ticket and decide to which ANet team it goes. Player classifications aren’t going to correct a lot of the time.
So don’t worry too much about the choices you make when using the in-game /bug tool. Do worry about the details you include in the description: do you best to make it possible for ANet to follow your footsteps so that they can recreate the conditions that you experienced. If you can, then they can figure out what caused the bug, and resolve it … regardless of how it was classified.