On Mar 20, 2009, at 12:51 PM, Josh Thompson wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Sometimes, we run across a really minor issue while working on a
issue. Rather than creating a JIRA issue for each of these minor
do you think about creating a catchall issue for each component/
combination (i.e., issue for frontend v2.1, issue for backend v2.1,
frontend v2.2, etc). Then, when something minor comes up, the
commit is tagged with the catchall issue number for that version.
This way, the bugs are still tracked, but we don't have to create a
issue for things like a regular expression that should have used a +
of the * that was already being used.
I'd also suggest that the catchall issue not be created for a
component/version until it is needed.
That strikes me as a bit of an overkill. For example, if you see a
variable that can be named a little better or if there's a spelling
error then I don't see the need to file a Jira at all.
In my opinion Jira is, in addition to a tracking mechanism for what's
going into which release, a communication mechanism for developers to
announce what they feel needs to be done and who intends to work on
it; it's kinda a macroscopic thing. It is also a mechanism for the
community to officially make its wishes known as well as the usual bug