I've been with two very different companies that both use JIRA Tickets to track work done. The first was corporate company with some high standards when it comes to defining Tickets in Jira, the second a startup that merely writes down a description of needs to be done (Usually a one liner).
Now the second has caused some issues around defining what is expected, information relating about the work, finding out exactly what needs to be done and so forth. I am currently in a position where I can strongly hint or suggest better practices.
My question is - Is there a defined format/standard practice guide when creating Jira tickets to improve workflow?