mandatory fields on a per category base

I realise being a big change, but this is something that I'm still wondering why it is missing because it should be easy to implement, and yet extremely useful at the same time.

Depending on the Category, lets take the most simple: the Oracle Database category. The first obvious thing that comes to mind in database context is often: what database version does this issue relate to ?

It could be entered via a separate field, with pre-defined values. The database versions are known and there aren't that many. That is, if you only regard the first number.

So, in form of an LOV (List of Values), but what is important is that you also have a choice for when the version cannot be given. There can be may reasons for that, ranging from : unknown, uncertain, multiple versions involved (for upgrade purposes), questions which don't relate to specific versions, undisclosed information, etc.