[consulting] Issue tracker specs

[Morbus Iff]

> Okay, so here's a new thread, and here's a first stab:

And, I can talk about the Case Tracker end of things, though we
should probably bring dww in to chat more about project.module.

> * Issue ID# for each issue filed

Case Tracker uses non-node-ID "project numbers" and "case numbers" to 
create a unique complete "case number" [1]. Project numbers start at 100 
and increase by 100 (100, 200, 300), and case numbers start at 1 and 
increment by 1 uniquely for each project [1]. Thus, the third case in 
the fifth project would have a case number of 500-3. There's a "Jump To" 
block to jump directly to a case number, and I'll be making a URL option 
once I fiddle with that area of the code (such that casetracker/ goto/ 
500-13 would do the right thing).

> * Email-in issue, with autoreply citing issue #

Handled via mailhandler.module, but as mentioned before, I've not tested 
this part of the code, so can't speak to how well it works. I will 
continue to support it, however.

> * Permissioning on responses -- in-house responses vs. responses  
>    client can see (so internal discussion can happen in-line)

Not currently planned, and would be a bit difficult to do, I imagine. 
Case Tracker uses Drupal comments, and comments don't have a per-comment 
access system, like a node_access.

> * Basecamp-like basics: file uploads, milestones
 >  (for development projects)

In Case Tracker, file uploads are handled via upload.module and 
comment_upload.module. Milestones could be handled via an event.module 
case node type (which I'm using internally in my own design, but have 
not fully tested to work out the kinks).

> * OG or other compatibility to keep client areas separate and private

I've discussed this previous, but yes, Case Tracker allows this.

> * Configurable status indicators (awaiting client
 > response, confirm closed, etc.)

Case Tracker allows custom status states in "Priority", "Status", and 
"Type". It does not allow the creation of entirely new categories.

> * Permissioning on status indicators (so clients
 >   cannot arbitrarily change status)

Case Tracker allows this on Status (so that, say, only developers can 
"Close" an issue) and "Assigned To", but on nothing else. It'd be 
trivial to add it to the other state types, however.

[1] It's not actually working as designed due to some bugs left behind 
from the previous developers, but I'll be fixing that up when I get 
situated again. Probably a few weeks from now.

-- 
Morbus Iff ( omnia mutantur, nos et mutamur in illis )
Technical: http://www.oreillynet.com/pub/au/779
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus