Master-detail navigation in planning/task boards

[Andrew Thomas]

In the planning and task board, I can bring up a detail view of an issue. (For example, via the "Edit in JIRA" action or the link with tooltip "View this issue in JIRA".)

There used to be an easy, single-click, obvious mechanism to exit the detail view, and return back to the prior context -- via a close button in a corner. No thinking was required.

In 4.4.1, that obvious, single-click mechanism for exiting the detail view seems to have been lost.

Workarounds:

* Use the browser back button to step back until finding the planning or task board.

* Find "More Actions" button in the vast middle, click it, look for "Planning Board" or "Task Board, think about which one we were at before, click it.

Am I missing something? Is there a setting to open the detail view in the old dialog-like manner?

(By the way, I realize JIRA and GreenHopper began as separate products. However, it seems like integration should improve over time.)

[Jon Cotter · Accepted solution]

I too struggled with this for a bit. I found that if you just click on the Agile tab (just the word Agile, not any of the submenu items) when you are done viewing your issue, you should get back to the exact Planning or Task board view that you left from.

[Andrew Thomas]

Thanks, Jon Cotter! That's better than using the "More actions" button.

However, it's still a regression that would be nice to have fixed:

* It doesn't lead you back to the same page of the planning or task board. Even if you had been on page 2, you get sent to page 1.

* For exiting the detail and returning to the master, the "close" button was easy to understand and find, the "Agile" tab less so.

[Jon Cotter]

Aha. I didnt notice that about the paging... i miss the old iframe/lightbox structure... i used to just hit ESC and would return back to my list with everything exactly as it was (and without that annoying page refresh that using the close link caused).

Hopefully their UX people are on top of it

[Andrew Thomas]

I added this issue to Atlassian's JIRA: https://jira.atlassian.com/browse/JRA-25761 .