It has been like that since at least ITSM 7.0.  I'm guessing it is related to 
aesthetics as you mention.

-Patrick



|  -----Original Message-----
|  From: Action Request System discussion list(ARSList)
|  [mailto:arslist@ARSLIST.ORG] On Behalf Of SUBSCRIBE ARSLIST theReel
|  Sent: March 27, 2013 10:13 AM
|  To: arslist@ARSLIST.ORG
|  Subject: Whats with the Classification field labels in 8.1
|  
|  Hi Guys,
|  
|  Time to let off some steam.
|  Just having a look a the classification tab that has been added to the Best
|  Practice View of Incidents in 8.1.
|  For the Operational Categorization Tier 1 - 3 and Product categorization
|  Tier 1-3 fields the display labels of the fields have been hidden behind
|  other fields and then separate text fields added where the labels would have
|  normaly been.
|  
|  Does anyone have any idea why on earth this has been done and why the labels
|  are not visible as normal?
|  The product Name, Model, Manufacture labels are all laid out as normal.
|  
|  This will affect users when they try to do an avanced search and click on
|  the field label expecting it to be added to the search bar but it will not
|  work.
|  
|  Also this highlights a bug of mine and many of my users - the name of the
|  actual field is ''Product Categorization Tier 1" but the label is Tier 1.
|  Which means when users unfamilar with the field names try to do a search,
|  report, filter or look in the audit log they cant find the fields they want
|  as the labels are different. My favourite one is the "Problem coordinator"
|  field which shows up as the "Assignee Pblm Mgr" in the audit log.
|  
|  As I write/rant I think I know why it has been done in the incident form -
|  it is for asthectic reasons - i.e it doesnt look pretty having a list of
|  long labels:
|  Product Categorization Tier 1
|  Product Categorization Tier 2
|  Product Categorization Tier 3
|  It might not look pretty but at least the usability would have been better!
|  Why not shorten to Product Cat Tier 1.
|  
|  I notice in the change module they have named the fields Tier 1 - 3. But
|  then most things seem to be done differently accross the modules. eg. how
|  the customer is selected is wildly different in Incident and change.
|  
|  Note to any BMC readers:
|  Please try to keep labels, Db names and visble labels the same Please get
|  the change/incident/problem teams to look at the other modules and keep them
|  some way similar at least in the end users eyes.
|  
|  And breathe.  Sorry about that folks, I just had to get it off my chest.
|  
|  Tony
|  
|  ____________________________________________________________________________
|  ___
|  UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers
|  Are, and have been for 20 years"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to