Required on close
It would be useful to have a check item on issues related custom fields that force tha this field is mandatoty to fullfill when the issue change to a state registered for close.
It would be similar to the actual required field but only for the closure of the issue.
#2 Updated by Mikael Rudberg about 9 years ago
+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
state : Assigned
field : Target Version : Required
field : Affected version : Optional
#3 Updated by Nick Read about 9 years ago
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.
#7 Updated by Nick Read almost 9 years ago
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 :(
#15 Updated by Mischa The Evil over 4 years ago
- Subject changed from Requiered on close to Required on close
- Status changed from New to Closed
- Resolution set to Duplicate