##Summary
To keep teams in sync and working quckly all project / work / issue conversations should be documented in Trello, and not in emails, chats, etc.
If you have a future feature idea, or bug to report - put it on Trello and you can safely assume it's on the design / dev team's radar. If you need immediate response or feedback, reference the team member with the @ sign.
##Documenting a Future Feature / Bug Report in Trello
- If relevant, take a screenshot of your whole screen (full browser window) where you're experiencing the bug or envisioning the feature.
- Go to Trello find your project's board and click "Add a card" in the appropriate column. (Not sure what the right column is? Default to the furthest left column and ask your team!)
- Name the card with a short summary of the feature / bug.
- Click the green "Add" button.
- Click your freshly made card again to bring up a window where you can add more information and attachements.
- Click the "Edit the description..." link and describe the feature / bug.
- If relevant, use the "Attachment" link on the right to include screenshots, mock ups, etc to help explain the feature / bug.
- Feel free to ask questions or start discussions in the column feed at the bottom of the card (and take advantage of the @ feature to notifiy a specific teammember that you've got a question for them.
##More Info
##Source of Truth
Since most development and design work is taken directly from the project's Trello board it's important to treat it as the "single source of truth." Any chunk of work that needs doing (even far future work) belongs on Trello, and decisions made about that piece of work must be on Trello. This keeps teams in sync.
Trello cards should also house links to all of the assets (images, copy, urls, etc.) necessary to complete the work defined on the card.