Traditional issue trackers and collaboration tools lock you into their form-based straightjackets. Start with plain text, then add the structured data that you need. Drop in common attributes (like status or severity), timeclocks, wireframes, or even video or text chat windows.
Many tools mean many information silos, and jumping between tools introduces friction into collaboration. Run code, video chat, message, whiteboard, all in the same unified document. Everything gets saved as documentation.
All documents, and their rich context, live on as wiki-style documentation long after development is done. Why write separate docs when the whole story of a bug or feature already exists in your issue tracker?
Start simply with a plain-text description of your feature request or bug report. As development progresses, add in only the structured data that you really need.
Remove barriers to collaboration by unifying communications into one interface. All communication happens in-document. Communication is saved and lives on as documentation.
Collaboration and communication produces artifacts that are stored in-document. Refer back to the real reason it is like it is, not a later interpretation.
"Business is all about the customer: what the customer wants and what they get. "
" I've internalized it to the point of understanding that the success of my actions and/or endeavors"
"The American Dream is that any man or woman, despite of his or her background, can change their circumstances"
"Generally, every customer wants a product or service that solves their problem, worth their money"
"No one can make you successful; the will to success comes from within.' I've made this my motto."
"Can change their circumstances and rise as high as they are willing to work"