(In reply to comment #0)

This will probably need to be filed upstream, unless somebody on our end can
create a patch.

Indeed.

Is OTRS in Puppet? I think there are differences between how much we can customize software that is or isn't deployed via Puppet. Jeff G. would know for sure. Depending on how annoying this is, we can probably find a workaround for now and work on a ticket upstream simultaneously.

For tickets upstream, just go ahead and file the bug there (in OTRS' issue tracker). Be sure to search their tracker first because the issue may already be filed/reported. Then mark this bug with the "upstream" keyword and cross-reference the upstream bug report link.

If you really think this is a problem, a workaround would probably be to toggle Ticket::Frontend::MoveType from Dropdown to New Window via the SysConfig, see also http://doc.otrs.org/3.2/en/html/Ticket.html#Ticket:Frontend::Agent::Ticket::ViewMove (attention, large page). (I'm a bit worried about Ticket::DefaultNextMoveStateType -- the state should ideally not be changed when moving a ticket. Could this be achieved by setting Ticket::Frontend::AgentTicketMove###State to No? It's currently Yes.) As far as I see, this would basically get us back to how it was handled in 2.4.

That said, I do like the simplicity of the dropdown and can't remember to have made a mistake here, So I'm just not sure if this is actually a "bug." Perhaps we can collect some more opinions on OTRS Wiki?

It is a minor issue/enhancement - all such requests go to bugzilla. I posted this after report/request of a number of users. If you'd like more discussion, feel free to start one.

People frequently make mistakes. Many times they ask for the ticket to be moved back. Other times they just leave it. This would eliminate any potential for issue with very minimal action required from the agent (one extra click or pressing of 'enter').

Closing. An alternative is built in to the software but the agents aren't interested in changing the option at this time.