Changing Component changes Owner

[euzuro]

I am doing some work on an AJAX library that interfaces with TRAC (via httprequest).

I have concluded that if you have a ticket whose owner is set to the same value as its component's default owner (say for example, your ticket has component "TicketCalendar" and owner "euzuro")

then when you change it to another component which has a default owner, the owner of your ticket gets changed.

I notice also that once the ticket has been "accepted", this no longer happens.

In the end, I figure there are valid reasons both for and against this, so I'm not sure if you'll consider it a bug or not.

[anonymous]

Merely to illustrate, note in the change history for this ticket how the owner has changed from jonas to mgood and now back to jonas.

[Christian Boos]

Well, what I'd rather address is to not make it possible to explicitly set the owner. I don't think its relevant for the reporter of a problem or enhancement request to target who will address this, unless the reporter is himself a developer or manager (and hence has the TICKET_ADMIN rights).

[euzuro]

agreed. that would be a nice feature. it wouldn't, however, resolve this problem — at least not for those with admin rights ;-)

[Matthew Good]

This is the intended behavior. Tickets in the "new" status which were assigned to the default owner of the old component will be assigned to the default owner of the new component. If the ticket's been "accepted" or reassigned to someone else the owner will not be changed. This is to make sure that tickets entered with the wrong component get reassigned to the right person when the component is changed.

cboos: I don't understand what that has to do with this ticket. I know that there has been discussion before about being more restrictive about changing the owner, so there may be another ticket about that, though it may require the WorkFlow changes to address appropriately.