Require a problem description in issues
Currently some issues are just code examples without a description **why** a change should be done. This leads to problems when (years later) the current behaviour is questioned and no one can remember why it was changed.

I think it may better to be added:
- checkbox whether the reporter uses the latest version
  - reason otherwise

needs discussion though
 In Addition to the reason why the thing is actually a problem?
 @jorisvandenbossche @TomAugspurger 
 See also https://github.com/pydata/pandas/pull/14031 for basically the same thing for PRs. That one also has a small example why I think such a description is needed.
 The addition seems fine to me.
 ok, let's see how this works.

thanks @janschulz 
