Could you be more specific with how you produce this problem? Are you clicking the Change Status button, or the Assign button.

(The screen shot is missing).

Sorry but my problem is always here...when i feedback a mandatory multiselect list custom field, an error appars :
'A necessary field 'Type of issue' was empty. Please recheck your inputs.' and my field is set to blank...

For information i click on 'Change Status to' (with feedback selected)
But when i use update issue all is good.

From 0005558, This problem appears when i click on "Assign To", but it 'works with "Update issue".

This is curious. The code for bug_assign does not change, nor care about custom fields. Can you provide more details as to how you found this problem? What version of software are you using?

Sorry but the only one detail that i can give you, is the following :
I have configured a 'multiselect list' custom field has : 'Required On Update'
I click on 'Change Status To:' with 'feedback' selected, i write my note and click on 'Request Feedback'

After this action i have an error and my attribut is empty...

Can you reproduce or confirm this.

If the field is required, it should show up on the change status page.

I think that this is a duplicate of 0005527.

i will try to use the CVS page 'bug_change_status_page.php -> 1.21', but i'm not sure that is the same problem...
Because i have update the issue and i want to feedback from everyone. It's the feedback page which don't work correctly.

I'm confused. Is the field "Type of issue" (one of your custom fields) showing up on the "Request Feedback" (bug_change_status_page.php)? If not, is the field set as "Required for Update"?

My custom field is "Required for Update" and it appears when i want update an issue. In this case all is good.

When I choose to feedback an issue :
I choose the person to affect,
I write a note,
I click on button "feedback"

But an error appears wich says "A necessary field 'Type of issue' was empty. Please recheck your inputs." and my field is set to blank...

Some news?

Any news here? This issue has been assigned for years without activity...

I did not manage to reproduce this behavior in 1.2.11.

• define multiselect custom field, with values a|b|c, no default, displayed on report+update, required on update

• report new issue, leave the custom field blank

• change status to feedback, do not select value in list, click button
  ==> error 11 necessary field empty appears

• edit bug, click update
  ==> error 11 necessary field empty appears

so, behavior seems consistent and to work as expected.