Redmine

+1 This would be great for requiring a field like 'resolution' on close.

+1 for me too it would be even better if you could have a connection on all to state so for instance you could tell which fields where required for a particular state as in ClearQuest

e.g.

state : Assigned
field : Target Version : Required
field : Affected version : Optional
etc. etc.

Stephanie Collett wrote:

+1 This would be great for requiring a field like 'resolution' on close.

I'm interested in this for the exact same thing. At the moment I have patched our system to have a hard-coded check for moving an issue to a closed state without the custom "resolution" field being set.

Felipe Campo wrote:

Jean-Philippe , the version erase means that the Feature was dismissed ??

I suspect it means that version 0.8 is being finalised, and that this feature has not yet been implemented so it won't be there. That doesn't mean that this will not be implemented in the future though - I'm watching this issue with anticipation personally. If I had more time I'd write a patch..... ahhhh, the memories of once having spare time are starting to come back to me :(

Felipe, Nick is right.

+1

+1

+1

+1

I too need the ability to "require" a field to be filled in for the ticket to change state. Any chance we can get this feature?

I too need the ability to "require" a field to be filled in for the ticket to change status
even #5686 created.