Missing owner on new tickets

[Bill Buklis]

Recently I migrated our trac system to a new server and updated to
version 1.0. Everything seems fine except that for some reason the owner
is not getting set when creating new tickets. I have an owner specified
for every available component. When users create new tickets they also
select an appropriate owner. This used to automatically assign the
ticket to the correct owner who would get notified by email. But, now
the owner isn't getting set even though the component field is filled in.

It's been a while since I installed trac, so maybe I'm just missing a
simple setting somewhere that I've forgotten about.

Trac version details:

Trac 1.0 running on Windows Server 2008 under tracd. Database is sql lite.

Thanks,

--
Bill

[RjOllos]

On Tuesday, December 18, 2012 9:44:03 AM UTC-8, Bill Buklis wrote:

Recently I migrated our trac system to a new server and updated to
version 1.0. Everything seems fine except that for some reason the owner
is not getting set when creating new tickets. I have an owner specified
for every available component. When users create new tickets they also
select an appropriate owner. This used to automatically assign the
ticket to the correct owner who would get notified by email. But, now
the owner isn't getting set even though the component field is filled in.

If your issue was only that the component owner was not being set as the ticket owner, then I would suggest: There was an issue recently on IRC which was solved by removing the `[ticket] default_owner` entry from trac.ini. If the entry is not present, or if the somewhat awkward value < default > is entered, the default owner will be the component owner.

http://trac.edgewall.org/wiki/TracIni#ticket-section

http://trac.edgewall.org/wiki/TracTickets#DefaultValuesforDrop-DownFields

However, since you also say that the owner is not being set when explicitly selected by the user, I am not so sure. Just a guess, but maybe this problem is somehow caused by default_owner being a blank entry. Please let us know what your entry for `[ticket] default_owner` is, and we can take it from there.

[Bill Buklis]

On 12/22/2012 8:59 PM, RjOllos wrote:
>
> However, since you also say that the owner is not being set when
> explicitly selected by the user, I am not so sure. Just a guess, but
> maybe this problem is somehow caused by default_owner being a blank
> entry. Please let us know what your entry for `[ticket] default_owner`
> is, and we can take it from there.
>

Just to clarify: the problem was when the component was selected by the
user. I also always have a default component selected, so this entry
can't be be blank. I can't recall if I tried specifically selecting the
owner. Probably didn't, so I bet that would have worked.

Looking at thew "new ticket" page now (after fixing the default_owner
field) I can see that the owner field shows "< default >". No idea what
it showed before the upgrade. I didn't pay attention to it. It was
probably blank.

--
Bill

[Bill Buklis]

On 12/22/2012 8:59 PM, RjOllos wrote:

On Tuesday, December 18, 2012 9:44:03 AM UTC-8, Bill Buklis wrote:

Recently I migrated our trac system to a new server and updated to
version 1.0. Everything seems fine except that for some reason the owner
is not getting set when creating new tickets. I have an owner specified
for every available component. When users create new tickets they also
select an appropriate owner. This used to automatically assign the
ticket to the correct owner who would get notified by email. But, now
the owner isn't getting set even though the component field is filled in.

If your issue was only that the component owner was not being set as the ticket owner, then I would suggest: There was an issue recently on IRC which was solved by removing the `[ticket] default_owner` entry from trac.ini. If the entry is not present, or if the somewhat awkward value < default > is entered, the default owner will be the component owner.

http://trac.edgewall.org/wiki/TracIni#ticket-section

http://trac.edgewall.org/wiki/TracTickets#DefaultValuesforDrop-DownFields

However, since you also say that the owner is not being set when explicitly selected by the user, I am not so sure. Just a guess, but maybe this problem is somehow caused by default_owner being a blank entry. Please let us know what your entry for `[ticket] default_owner` is, and we can take it from there.

Thanks, I did eventually figure it out after some extensive google searching. Sorry for not updating on the list. That was exactly the case. There was an entry for "default_owner" and it was indeed blank. I've never added or modified this field, so I can't say how or when or even if it was changed. I changed the entry to "< default >". I'm guessing that the behavior of this field changed with the 1.0 version and this is why component owners were no longer working. Don't know...

Anyway all is good now. Thanks.

-- 
Bill

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02.01.2013 20:05, Bill Buklis wrote:
> I'm guessing that the behavior of this field changed with the 1.0
> version and this is why component owners were no longer working.

Yes, I assume the same.

Steffen Hoffmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDkisIACgkQ31DJeiZFuHdueACdEseflxX8EJQ/c0fNxSUxo+hK
c4YAn2kyLrAnqB+PTJwOyRPNq5Wi6R/x
=qZy0
-----END PGP SIGNATURE-----