I'd like to advocate the use of issue-tracking software within an organisation that currently does not use it.
But there's one aspect of their situation for which I'm unsure of what to suggest: their projects frequently receive informal verbal feedback or casual comments in meetings or in passing from a wide group of interested parties, and all this information needs to be recorded.
Most of these messages are noise, but they're vital to record and share with developers for two reasons:
- Good suggestions often come out of this process.
- It can be necessary to have evidence of clients' comments when they forget previous instructions or change their mind.
Is this the sort of information that should be stored in an issue-tracking system, or kept apart in a separate solution? Can issue-tracking system have good support for this sort of unstructured information?