495961 - assignToDefaultOnChange(['product', 'component']) should be optional

Status: RESOLVED WONTFIX

(Bugzilla :: Bugzilla-General, defect)

Description

[a.zhao]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: 3.2.3

My user base voice their biggest objection to the latest 3.2.3:

When the product/component is changed, the assignee is automatically set to the default person of that project - which is messing up the work flow.

Can this line of code be controlled by a setting parameter? Currently this is what I have done:

Modified template/en/default/bug/edit.html.tmpl: remove following 3 lines:

       <script type="text/javascript">
         assignToDefaultOnChange(['product', 'component']);
       </script>

This will disable the default behavior. 

Reproducible: Always

Steps to Reproduce:
1. Edit any existing bug
2. Change either product or component field to something different
3. The "Reset Assignee to default" checkbox will show up, and enabled by default
Actual Results:  
The assignee will be reset to the owner of the project/component

Expected Results:  
Do not reset automatically, and made it a optional setting.

Comment 1

[Frédéric Buclin]

There should be no parameter, and the feature shouldn't be turned off. What should be done is to only reassign if the current assignee is not the default one for the current component.

Comment 2

[a.zhao]

But (In reply to comment #1)
> There should be no parameter, and the feature shouldn't be turned off. What
> should be done is to only reassign if the current assignee is not the default
> one for the current component.

But this behavior is exactly what my user base vote against. 

This is the logics: there are times when some bugs need to be worked on by multiple teams of different product/component. When this happens, the assignee is already set with regardless of product/component. When product/component is updated, the original assignee should not change. 

After I upgraded from v3.0 to v3.2.3, there are already several cases where user changed the product/component, and in the same time unintentionally assigned the bug to a wrong person (the default person). They reported to me asking to turn this behavior off completely (they called it a bug, in fact).

Please consider to add an option to handle this situation?

Comment 3

[Frédéric Buclin]

No, adding an option is WONTFIX.

As I said, if the assignee is not the default one, it shouldn't change. In all other cases, it should. And you can already uncheck the "Reset Assignee to default" checkbox if you don't want to change the assignee, so another option is not needed.

Comment 4

[Max Kanat-Alexander]

Yeah, you can uncheck the boxes. assignToDefaultOnChange just checks the boxes, and it makes them bold so it's very obvious they've been checked. It's like one line to comment out if you want to customize it locally.