Content
View differences
Updated by Henriette Darge over 1 year ago
As part of the on-going work on removing the Angular-based UI router, we are considering removing the back button that's currently visible in work package details view:
<img class="image_resized op-uc-image op-uc-image_inline" style="width:504px;" src="/api/v3/attachments/209625/content">
**Reasons for removing it:**
* It's inconsistent. Takes the user:
* sometimes back to where they came from (same as the browser back button),
* sometimes back to the hierarchichal parent (if you come from a board, back to the board), but not if there's a hard reload in between reload
* It's unnecessary. The user can use the browser back button or other navigation cues.
* It takes up precious space in the header.
* It's based on the UI-router, so if we want to keep it, it's extra work to re-implement it.
**Reasons for keeping it:**
* Some users are used to it.
* We don't proper breadcrumbs for work packages yet (that also works with parents).
* It's useful in mobile:
* For getting back to the hierarchical root: this will however be fixed once we have the new "split-screen" based work package details view we already have in Notifications center, with the close button.
* (Not needed for going back; mobile browsers also have a back button)
**Suggestion:**
* On balance, we think it's better to remove it.
<br>
<img class="image_resized op-uc-image op-uc-image_inline" style="width:504px;" src="/api/v3/attachments/209625/content">
**Reasons for removing it:**
* It's inconsistent. Takes the user:
* sometimes back to where they came from (same as the browser back button),
* sometimes back to the hierarchichal parent (if you come from a board, back to the board), but not if there's a hard reload in between
* It's unnecessary. The user can use the browser back button or other navigation cues.
* It takes up precious space in the header.
* It's based on the UI-router, so if we want to keep it, it's extra work to re-implement it.
**Reasons for keeping it:**
* Some users are used to it.
* We don't proper breadcrumbs for work packages yet (that also works with parents).
* It's useful in mobile:
* For getting back to the hierarchical root: this will however be fixed once we have the new "split-screen" based work package details view we already have in Notifications center, with the close button.
* (Not needed for going back; mobile browsers also have a back button)
**Suggestion:**
* On balance, we think it's better to remove it.
<br>