Remember location in ticket list.

[sstanai]

When browsing a large list of tickets, my users must right-click any ticket they wish to open and click 'new window' or 'new tab' so that they do not lose their place in the list.

If they simply click the ticket, and then go back to the list, they always start at the first page in the list instead of the page they left on.

Can you please make it so that leaving a ticket will return you to the exact page of tickets the user originated at?

Thanks!
--SJ

[joegeck]

Copied from your other thread where this idea originated from.

Originally Posted by joegeck

...but I believe the ticket lists are generated dynamically through some type of AJAX call. And as far as I know using AJAX on web applications can have an impact on how the 'Back' button in your browser traditionally operates. The fact the list resets is a result of this behavior and I'm pretty sure there's no workaround.

1) My original assessment of the issue was wrong, I spoke to a developer and it's not a technical problem at all. In fact you'll notice that if you try using the 'Back' button from other places such as tickets in (home) Workspaces, it WILL remember your place in the list.

It turns out the "broken" issue is intentional design for all the 'mail' tabs: 'Workflow' and 'Overview'. It's supposed to reset back to the top page typically so you can still see the oldest tickets needing attention (by default, ticket lists are sorted oldest to newest). What I can do is go ahead and still file a new feature request disputing this design on your behalf. This will let the developers know it's not desirable for everyone, but fair warning, because this is intentional behavior you may never see an official change from us...

[Overview / Workflow] Go back to the correct place in the ticket when refreshing the 'mail' tab
http://www.wgmdev.com/jira/browse/CHD-1638

Originally Posted by sstanai

Advised my users to right-click the ticket and 'open in a new tab' for the time being... Going to submit it as a feature request. Thanks!

2) As a general rule, if you're going to file a feature request on your own go directly to JIRA and add it in officially in a bug report (like I just did). All requests eventually make there way to JIRA so all you did was re-post this same idea in the 'Feature Requests & Bug Reports' forums for someone else to move later.

Ironically, that person is me so you inadvertently created extra work for both of us I realize this was an odd situation: you asked in the 'General Help' forums first, got a response from me that it's not possible, and then decided to "bug it" it in another thread. Not your fault, but next time go for JIRA first.