[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579714#comment-13579714
 ] 

Jessica Tomechak commented on CLOUDSTACK-1285:
----------------------------------------------

The guideline we used for the first round of tooltips was 100 characters 
maximum. "A name for the zone" is too short. It tells you nothing useful - just 
restates the name of the field. Knowing what the name will be used for is 
helpful. Knowing whether this is a new name you're supposed to come up with 
yourself, vs. a name that has to match some already-existing value, is also 
helpful. The advice about best practices for choosing a good name might 
admittedly be overkill. I'd suggest something in between, like "Give the new 
template a name. This name will be visible to users."
                
> UI -Tooltip - Lengthy and inconsistent description among toolips
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1285
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1285
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc, UI
>    Affects Versions: 4.1.0
>         Environment: RHEL 6.3 Build#15
>            Reporter: Parth Jagirdar
>            Priority: Minor
>         Attachments: 3.jpg, 4.jpg
>
>
>  "A unique name for the template. This will be visible to users, so choose 
> something descriptive" ; I think 94 Characters are too much for a ToolTip 
> representing name. (Screen 4)
> And is also inconsistent with other tooltips for names which are more concise 
> and simple such as "A name for the Zone". (Refer to Screen 4 and compare it 
> to Screen 3)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to