Redmine

This will be much more user friendly !
+1

Related to #4637.
This is a must have feature. It's quite common users don't understand the meaning/purpose of an Issue field/option, and have that info centralized into a wiki page is not effective at all (needs constant update every time the set of fields or their meaning changes; the users are not aware of those changes).

Every Role, Tracker, Issue Statuses, Custom Fields, and Enumerations should all have a short description (wiki format would be great) of their purpose/usage. Then, that description could trigger a tooltip when hovering the field (maybe not totally viable for enumerations, combo-boxes), or perhaps be part of a consolidated Help page where those fields would appear.

+1

paulo ferreira: I agree with this. I also missed descriptions for custom fields. But you are right, there should descriptions for other objects too.

In another bug tracking system I remember (a long time ago) the labels for the fields were optionally hyperlinks to a popup page describing the field. It's a bit Web 1.0 - but then that was the time! If the field had a defined description, then the label was hyperlinked, causing it to be underlined so the user had a visual indication that the label was clickable. (This was before CSS and before websites started changing the look and feel of hyperlinks!)

Personally, I don't care whether it is a tooltip (although they are limited in length in most browsers), a hover-triggered div (aka a tooltip, but without the length limitation), an div that expands under the label when you hover or click on it, or a popup window.

+1

The 30-chars-Input is sometimes just not enough to explain the meaning of the field. Another point is that you can't use special characters.

I would prefer the a kind of "hovering popup" that shows up when you select the input field. This way it the user always has the explanation directly in front of him.

Another nice feature would be a the possibility to emphasize special custom fields, because we use them in a very excessive way and not all of them are that important to fill - But other way round, we can't make them mandatory.

Hi

Is there any solution for this feature request?
If so can anybody please refer me to it?
If not - will you consider putting it into the roadmap?

Thanks !
-- Amit.