[Tickets #4920] Re: Expose links to type/state/priority/attribute definitions (site-specific help)

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4920
-----------------------------------------------------------------------
 Ticket             | 4920
 Updated By         | php at ideacode.com
 Summary            | Expose links to type/state/priority/attribute definitions (site-specific
                    | help)
 Queue              | Whups
 Type               | Enhancement
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


php at ideacode.com (2007-01-21 09:06) wrote:

> It makes more sense to me to use title attributes for the 
> descriptions. These should theoretically even work for select boxes.

For simple definitions, that would work.  However, we expose a good deal
more information than could fit in a title attribute. For example, our
issue tracking overview:

https://mail.ideacode.com/wicked/display.php?page=IssueTracking

shows that tables and images are vital information in our case.

Perhaps a middle of the road approach would work.  Provide a text input
field and a select with two options: description and external link.  If
you type text and select description, the text appears as a title
attribute; this would be the default.  If you type text and select
external link, the text is treated as a URL to the appropriate
documentation and the appropriate links are rendered.