Navigating back just once after clicking a sub-task in the queue view of a ticket is not enough to back to the actual parent ticket.

Issue Summary

Navigating back just once after clicking a sub-task in the queue view of a ticket is not enough to back to the actual parent ticket.

Steps to Reproduce

1. Create a new issue in a Service project;
2. Through a queue, access it. The URL should have the queue breadcrumbs (ie instance/jira/servicedesk/projects/PKEY/queues/custom/1/PKEY-999);
3. Create a new sub-task for that ticket;
4. Click the sub-task box (but not it's actual key)
5. Navigate back on the browser

Expected Results

You're returned to the parent ticket;

Actual Results

You're left on the same sub-task.

Notes Checking the URL during the process you'll notice it changes twice:

1. From the original ticket: instance/jira/servicedesk/projects/PKEY/queues/custom/1/PKEY-999
2. To an intermediate state: instance/jira/servicedesk/projects/PKEY/queues/custom/1/PKEY-999?selectedIssue=PKEY-1000
3. Then to the subtask: instance/jira/servicedesk/projects/PKEY/queues/custom/1/PKEY-1000?selectedIssue=PKEY-1000

This intermediate state will display inconsistent data, such as the sub-task summary while listing the parent's childs.

Workaround

• navigate back again;
• open subtask by clicking the sub-task key as you're directed to it's instance/browse/PKEY-0000 URL without queue breadcrumbs