example enterprise workflow disables component assigned ownership

[pottingerhj@…]

It seems the functionality of the component system where ownership of new tickets is assigned based upon the selected component, assumes that the workflow in use will be the default Trac workflow. If you change your workflow to the enterprise workflow, and then configure a component with an owner, the owner will never receive e-mail messages about new tickets. Indeed, an owner is never assigned (by the component) to the ticket at all.

Details: Trac 1.0.1, on RHEL6, installed via the packages in the EPEL repository. Enterprise workflow enabled. I've tried the TicketCreationStatusPlugin (​http://trac-hacks.org/wiki/TicketCreationStatusPlugin) however, that doesn't change the fact that ownership is not getting assigned by components, so the TicketCreationStatusPlugin doesn't have a chance to do anything.

[Ryan J Ollos]

Replying to pottingerhj@…:

It seems the functionality of the component system where ownership of new tickets is assigned based upon the selected component, assumes that the workflow in use will be the default Trac workflow.

That shouldn't be the case. The behavior depends having [ticket] default_owner = < default >. Loading the enterprise-workflow.ini​ into the [ticket-workflow] section should not change this behavior. Am I correct to assume that is what you are referring to when you say enterprise workflow?

What is your value for [ticket] default_owner?

[pottingerhj@…]

Hi, we've recently upgraded from 0.12.2 to 1.0.1, the old value for default_owner is blank, I've changed it to your suggested value: default_owner = < default > and that works great! Thanks for the help!

[Ryan J Ollos]

Oh, right. This was discussed in #10825 and documented in TracUpgrade#Behaviorofticketdefault_ownerchanged. Sometimes I wish could remember things from day to day ;)