Trac do not auto-assign owner anymore

[Styx <styx7@…>]

Since I installed Trac 1.0beta1 Trac doesn't assign Ticket owner automatically as it was doing before with version 0.12.

I have a owner for each of the component of my project. I tried both mode : with and without the drop-down list : behavior is the same.

[osimons]

"With and without the drop-down list"? Trac only supplies drop-down list for the component field. What do you mean?

Anyway, I tested auto-assign through component owner against clean environments using both 0.12.4dev and 1.0dev, and both worked without problems. As far as I can tell nothing has changed, and all is as it should be.

This suggest perhaps a PluginIssue. Perhaps some plugin you have installed that is not compatible with some backend or frontend changes, and somehow interfers with the regular Trac handling in unexpected ways? Do you see the problem even if you disable all plugins?

[Christian Boos]

Replying to osimons:

"With and without the drop-down list"? Trac only supplies drop-down list for the component field. What do you mean?

I think he was referring to the owner drop-down (with [ticket] restrict_owner = true).

I also tested trunk with and without the owner drop-down, and it also worked as expected for me.

To the reporter: if you happen to have a reproduction recipe for this problem (e.g. starting from a fresh environment, describing the steps taken to get to the problem), please reopen.

[marco.comini@…]

I have the same problem. If the owner field of new tickets is left blank on creation (while the component is properly selected) then a ticket is created with "(null)" owner (instead of being assigned to the component owner).

This has 2 negative side-effects 1) the component owner is not notified of the ticket 2) when the ticket creator tries successively to manually edit the ticket to fix the problem, the "owned by" field does not show up

[Ryan J Ollos <ryan.j.ollos@…>]

This issue came up recently on IRC. In that case, the user just needed to remove the default_owner entry from the ticket section (TracTickets#DefaultValuesforDrop-DownFields).

[Christian Boos]

You beat me at it, I was about to figure out, but was not quite there yet ;-)

Indeed, the difference between demo-1.0 (where it doesn't work) and demo-1.1 (where it works) is that in the first case, [ticket] default_owner = (i.e. empty) whereas in the second we have [ticket] default_owner = < default >.

Well, I was never that fond of "< default >", I wonder if we couldn't pick something more explicit like component.owner (and bad luck for the poor user who also have that name…).

[Ryan J Ollos <ryan.j.ollos@…>]

Replying to cboos:

Well, I was never that fond of "< default >", I wonder if we couldn't pick something more explicit like component.owner (and bad luck for the poor user who also have that name…).

Yeah, I agree it is a confusing and error-prone notation. I assume the whitespace matters and its difficult to communicate that to someone over the mailing list or IRC, so in the case that it came up I just said to remove the entry, so that it defaults to < default >.

[anonymous]

This still causes problems when upgrading from 0.1x to 1.0.x (discovered in upgrade from 0.12 to 1.0.1). Ideally the "trac-admin <env> upgrade" command should set the default_owner to < default > if it was empty in 0.1x.

[Ryan J Ollos]

Replying to anonymous:

This still causes problems when upgrading from 0.1x to 1.0.x (discovered in upgrade from 0.12 to 1.0.1). Ideally the "trac-admin <env> upgrade" command should set the default_owner to < default > if it was empty in 0.1x.

That seems reasonable, but now that 1.0 has been released and the upcoming release is 1.0.2, it seems like it would be even more confusing to have the behavior-on-upgrade differ between 1.0 and 1.0.2. What about adding just adding a note to TracUpgrade? For example:

Prior to 1.0, the owner field of new tickets always defaulted to [ticket] default_owner when the value was not empty. If the value was empty, the owner field defaulted to to the Component's owner. In 1.0 and later, the default_owner must be set to < default > to make new tickets default to the Component's owner. This change allows the default_owner to be set to an empty value if no default owner is desired.

[Ryan J Ollos]

Replying to rjollos:

That seems reasonable, but now that 1.0 has been released and the upcoming release is 1.0.2, it seems like it would be even more confusing to have the behavior-on-upgrade differ between 1.0 and 1.0.2. What about adding just adding a note to TracUpgrade?

I've edited TracUpgrade in version 100.

[Ryan J Ollos]

#11495 closed as a duplicate.