We have a software project that we are trying to implement some basic project management for and we're starting simple, just using a Trello kanban board to track bugs/feature requests. I am beginning to transfer items from our in-house help desk system (which doesn't have any tracking features, it's basically just a record of user-submitted tickets with some searching and email built in) into a Trello board called "<insert product name here> Backlog". In this board, we have
Feature filters, as well as additional filters indicating what section of the app it relates to.
I'm conflicted on whether items should be worded as what is broken or as what work needs to be done. For example, if I have a help desk ticket that says "Financials on this page have a rounding error", do I create a card with that wording, or should I call it "Fix rounding error on
x page"? Or, as a third option, do I word it as what "should be"? I.e. "Page should have no rounding errors". Perhaps this is an X/Y problem and I'm trying to do too much with this board, but I don't know.
I am a developer turned accidental project manager with no prior PM experience, so any and all advice is appreciated. Not looking to become a scrum master here — I quite like software engineering — I just want to learn and implement some best practices.