[p4dti-discussion] Will setting "closed_state = NONE" stop P4DTI from closing bugs?

[Jay Glanville]

Hello all.
 
Sorry for the rather cryptic question, but I always have problems making
succinct subjects.
 
Here's the situation: we're currently using P4DTI to synchronize between
Bugzilla and P4.  Works great (Kudos to Ravenbrook)!  However, we want
to change once piece of behaviour.  It's when you submit a changelist
with jobs attached, that the job's status gets set to "closed".  Of
course, P4DTI picks up this change and resolves the bug.  But we want to
force the developers to resolve the bug explicitly.  (If they resolve it
explicitly, then they might remember to fill in the rest of the fields
that are asked of them.)

My though was that if we set the P4DTI configuration option
"closed_state" to NONE, then when the job was closed, P4DTI wouldn't try
to change the bug's status.  My fear is that when P4DTI tries to
synchronize information in the other direction (BZ -> P4), and the bug
was RESOLVED, would it properly set the job's status?

Will my proposed solution address our need?  Will there be any adverse
side affects?  Is there a better solution?  Or should we just live with
the behaviour as it is now?

Any feedback is appreciated.

Thanks

JDG
 
---
Jay Dickon Glanville