A JIRA issue tracking FAQ for a small team
This post is intended as a living document that will evolve and grow over time. If there’s something you think I missed or would like something clarified, please feel free to leave a comment.
Who should be reading this FAQ?
Managers, developers, testers, anybody working or contributing on a software project.
When should a small team be using an issue tracker such as JIRA?
A young startup may initially get away just fine by working informally and by email, and early in the project you’ll want to have as little administrative burden as possible, however as a project and team matures, there will come a time when having a searchable, persistent audit history of business decisions, fixes (and why they were done) and completed tasks will become invaluable.