|
I too agree on this. We use a "Solution" field for support requests. It would be very helpfull if that field could be shown (even required) when resolving an issue.
my vote is mostly based on two use cases:
1) when creating an issue, hide certain fields like 'fix version' which mean little to certain issue creators, yet still be able to edit these fields. 2) set a number of fields on resolve. This will be implemented in JIRA 3.2. Please see
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
We have "release notes text" as a custom field, so engineers are responsible for filling the information that will go into the release notes documentation.
By presenting this field when resolving an issue, the engineers would be reminded of this responsability. Otherwise, they may resolve the issue without having added this information.