Bug 1033386 - Unnecessary Groups list link above the group name
Summary: Unnecessary Groups list link above the group name
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: zanata-dev-internal
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-22 02:05 UTC by Damian Jansen
Modified: 2013-11-26 03:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-26 03:53:08 UTC

Attachments (Terms of Use)
Screenshot of error (22.01 KB, image/png)
2013-11-22 02:05 UTC, Damian Jansen 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Damian Jansen 2013-11-22 02:05:18 UTC 
Created attachment 827543 [details]
Screenshot of error

Description of problem:
There appears to be a "Groups" list link above the group name in the new group stats page. It could have been a breadcrumb, but doesn't look like it now.
That it does the same thing as the Groups link in the menu bar makes it unnecessary.

Version-Release number of selected component (if applicable):
dev

How reproducible:
Easy, always

Steps to Reproduce:
1. Sign in, go to Groups
2. Select or create a group

Actual results:
Above the group name is a link with the text "Groups"

Expected results:
Nothing there, it's superfluous.

Additional info:
See screenshot
Comment 1 Luke Brooker 2013-11-24 23:45:39 UTC 
It's not superfluous on small screens when the menu is hidden and eventually the menu bar might not contain the groups link on large screens. I was trying to give immediate recognition to what type of page this is as in the future projects will look similar but would have a "projects" link above.
Comment 2 Damian Jansen 2013-11-26 03:53:08 UTC 
After a talk with Luke, this is deemed intended behaviour.
Note You need to log in before you can comment on or make changes to this bug.