Changing bug assignee after using inline status/important editing reverts them

[Julian Edwards]

The new inline bug status and importance editing is great!

However, if you edit them and then change the assignee or milestone, it reverts the changes made in them since the expanding area contains the old values. :(

[Eleanor Berger (intellectronica)]

This is indeed very confusing, but I don't think we should put any effort into fixing this now, since the final goal is to get rid of the expanding section and do all editing inline.

[Martin Pool (mbp)]

When you get rid of the edit form, please bear in mind that it's very nice and very common to change these fields and at the same time provide a rationale for the change, to be sent in the same email. That works pretty well at the moment.

[Björn Tillenius (bjornt)]

On Wed, Jul 15, 2009 at 03:45:19AM -0000, Martin Pool wrote:
> When you get rid of the edit form, please bear in mind that it's very
> nice and very common to change these fields and at the same time provide
> a rationale for the change, to be sent in the same email. That works
> pretty well at the moment.

Yeah. I think we have to consider re-designing the AJAX-interface. I've
been using it to triage a few bugs, and while it's prettier, it's
actually slower for me than the old non-AJAX interface for the common
task of changing the status and importance, while adding a comment at
the same time.

[Julian Edwards (julian-edwards)]

> Yeah. I think we have to consider re-designing the AJAX-interface. I've
> been using it to triage a few bugs, and while it's prettier, it's
> actually slower for me than the old non-AJAX interface for the common
> task of changing the status and importance, while adding a comment at
> the same time.

While I initially thought "yes!", it might be worth a quick study to see if
this is the case, or if it's just perception.