Bug 1012228 - State controls for bulk update are opaque and confusing
State controls for bulk update are opaque and confusing
Status: NEW
Product: PressGang CCMS
Classification: Community
Component: Web-UI (Show other bugs)
1.1
Unspecified Unspecified
low Severity high
: ---
: ---
Assigned To: pressgang-ccms-dev
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-26 00:08 EDT by Ruediger Landmann
Modified: 2013-09-26 00:08 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ruediger Landmann 2013-09-26 00:08:31 EDT
Description of problem:
The state controls for bulk update are plain black circles that change to plan black circles with "+" or "-" markings on them if you click them. This is not a common part of the web UI vocabulary; it doesn't look like a control at all. 

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

How reproducible:
100%

Steps to Reproduce:
1. Click Advanced -> Bulk Tagging
2. Click Fields
3. Provide a topic map ID in the "Topic Included In Content Spec" field
4. Click "Tags"
5. Click a box in the first column and a box in the second column (what do these represent?)

Actual results:
A list of tags is presented with columns for "Search State" and "Bulk Update State" These columns contain featureless black dots that are actually the controls for including or excluding tags from the update. There's nothing to indicate these are controls, not even a tooltip.

Expected results:
Use common web UI vocabulary for these controls: radio buttons or a drop-down menu would make it immediately obvious that these are the controls for the page.

Additional info:
I thought these were status lights. "I wonder why all these tags are black?"

Note You need to log in before you can comment on or make changes to this bug.