I've never seen the old versions so I'm not sure on what I might be missing out on however I've come to appreciate the current methods after a while of using them.One of the features is the ability to generally do "everything" in just one go. Here are some examples:Claim the ticket and leave an internal note:- Use the claim button and enter the note in the window.Claim the ticket and send the client a response:- Use the reply button, the ticket is auto-claimed.Close the ticket and leave an internal note: Close the ticket and enter the note in the window.Close the ticket and send the client a response: Use the reply button, change the status to resolved.I absolutely agree however there are cases for which the system sending you back to the queue is frustrating, and that is when editing the ticket and occasionally when just posting an internal note before sending a reply. The trouble, however, is that sometimes I want the behaviour, and sometimes I don't it in these situations.Here is where a very simple bit of extra functionality provided by a PR comes in very handy.Enter one of my favourite PR's #3484: https://github.com/osTicket/osTicket/pull/3484 This puts a link back to editing the ticket again in the UI alert message similar to the one you have pointed at with the red arrow in your 2nd screenshot.This allows for a quick and efficient workflow, if you don't want to make more edits you are good to go, if you do it is a single click away to be able to start doing so again.It would be really nice if more of the UI alert messages used this format, however this PR address perhaps the most commonly used one which is for after adding an internal note.