According to the Harvesting pages, BFAV is "supposed to be" used only
for issues related to the image.  In practice BFAV is used to report
bugs on anything in SqueakMap.  This is actually very useful.  For
example, as one of the maintainers of BFAV itself, I find it helpful to
be able to screen for [BFAV] and see all the related bugs, fixes, etc.
As a bug reporter, it's nice to have one place to report all issues,
particularly since my diagnosis for which component needs changing may
be wrong.  

The main disadvantage of this approach is that it makes it hard for
someone looking for bugs/fixes/enhancements to the "image and nothing
but the image" to do so without sorting through all the "irrelevant"
posts.  I'm looking for ways to solve this problem.  Any ideas?

I think a good solution would address the following requirements:
-It makes sense to assume that a post is for the image until we know
better and therefore to make this the easiest thing to do. (Asking
posters to add [IMAGE] probably wouldn't work.)
-It makes sense to allow us to move posts back and forth between
"package assigned" to.  (The solution would probably be something like
the solution for reopening a post: last post wins.)
-We want an easy to find/understand/use list of package tags.  (Some
short tag tied to SqueakMap would probably be helpful).

I plan to address the issue of copying posts from one group to another
(split/merge groups)first.  But in the meantime, I would appreciate any
comments about the requirements or design for this aspect of making BFAV
and even better bug tracking tool.
Thanks
Tom