Done. The piece you were missing is that the categories are actually states in the collector_issue_workflow. I added a "Wontfix" state and a "refuse" transition (bringing to a total of three the transitions by which issues are dodged:), and hooked them into the existing lattice.
Yay! Does this mean we have a fully functional "wont fix" state now?
This was easy. Other issues with our collector/issue-handling process are not so easy (particularly the security controversy). I'm going to try to take some responsibility for getting attention on those issues, since i have a bit of between-deadlines breathing space.
Cool. Some kind of policy that we can point new-issue-resolvers at to clarify what should be rejected/accepted/wont-fix'ed would be really handy...
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
