Detail, detail, detail, context, context, context.
Tell where the feature request came from, as well as what it is. Tell us _why_ the client wants the feature.
If the request comes from an email or Slack message, paste that into the issue too!
Knowing why a somebody wants something done is almost as important, in terms of scheduling and planning features, as knowing what they want. Sometimes it’s more important, because often by knowing why somebody wants a certain feature, we can deliver them a better solution that they’d never even thought of, or we can aggregate a bunch of related requests into an über-solution that makes everyone happy.
Keep tasks small, i.e. < less than 8h if possible.