This especially applies to Trello tickets that you're writing to your own colleagues/developers.
Prior to going to DevBootcamp I worked as an engineering consultant, my product was informational reports that had to describe specifically what the problem was, how we determined that, and what we recommended to resolve it.
Sometimes my reports would be returned to me in a blood bath of red ink on changes but eventually you understand what it means to get the point across objectively and concisely.
My point is, get your copy proof read, limit the jargon, and get to the point in the first sentence.
Prior to going to DevBootcamp I worked as an engineering consultant, my product was informational reports that had to describe specifically what the problem was, how we determined that, and what we recommended to resolve it.
Sometimes my reports would be returned to me in a blood bath of red ink on changes but eventually you understand what it means to get the point across objectively and concisely.
My point is, get your copy proof read, limit the jargon, and get to the point in the first sentence.