Pragmatic Issue Tracking
I’m writing up an internal document to help sell the use of our JIRA issue tracking system. Right at the beginning I try and set expectations at a reasonable level for what a good issue tracking system really does.
You work on n projects, each having their own set of issues {x,y,z}. This work consumes T hours. JIRA does not decrease n,{x,y,z}, or T. JIRA tries to restrict the growth of T by reducing issue overhead that tends to increase certain values of T (meetings, duplicating work, confusion, etc.)
Does that sound about right?