Ticket set_owner lookup should be set to current owner by default

[anonymous]

For example, I have some statuses, for which in some cases I want to change owner, in other cases I want leave current owner. And will be usefull if by default this field will be set to current owner. The patch is very simple, I can attach it if you want.

[Remy Blank]

I don't really see how this would make sense. If you have set_owner, it's because you want to change the owner. I don't understand the use case where you want to have set_owner for a transition, but keep the current owner.

[anonymous]

For example, we have status "assigned". When the user create new ticket, the user change component. Ticket owner is set to the default owner for component. Then the head developer assign this ticket to developer to implement this feature. At this moment the owner may be right, but in other cases the head developer should assign this ticket to another developer. Now I can create two different statuses in workflow (one with set_owner, another without set_owner). But will be more easy to use only one status with set_owner if by default this field will be set to current owner.

[Remy Blank]

Replying to anonymous:

Now I can create two different statuses in workflow (one with set_owner, another without set_owner).

I was going to suggest exactly that.

But will be more easy to use only one status with set_owner if by default this field will be set to current owner.

The trouble is, most people prefer keeping the current default, so we won't change the set_owner action. You could implement a custom ITicketActionController component in a plugin, with the desired behavior.

[commerce@…]

Noting that #10018 is a duplicate. I commented over there that my team has this same problem. I think the responder/closer here didn't understand the need for this, so even though this ticket was closed, I'll restate our need.

We have a custom workflow state transition where sometimes the ticket editor wants to leave the owner set to current owner, but also sometimes wants to change it due to something that is inherent to the state change. Thus we want a state transition that allows conveniently changing the owner in one update step. But the editor is often in a managerial role, and that editor almost never wants to reassign the ticket to himself/herself. So the editor must almost always remember to change the owner back to the current owner (and may have to look this up before doing so).

This is pretty much what the person who opened the ticket said: "for which in some cases I want to change owner, in other cases I want leave current owner." The response by the person who closed it was essentially "I don't believe you." (Exact quote is "I don't really see how this would make sense. If you have set_owner, it's because you want to change the owner.")