On Mon, 2012-03-26 at 17:24 -0400, Ethan Jucovy wrote: > > http://trac.edgewall.org/ticket/7562#comment:7 > http://trac.edgewall.org/ticket/7562#comment:12 > http://trac.edgewall.org/ticket/7562#comment:13 >
I see the statement that text fields should never be linkified. Odd statement. What does one type into a search box other than text? I can agree that having it on globally and by default might be a bit much. But saying that text fields should never lead to a search seems rather draconian. > > There was some discussion of adding a ``linked_fields`` configuration > option that would let users turn on this feature for their own custom > text fields, but it looks like it was never implemented. (I can't > find any reference to "linked_fields" in a checkout of the Trac > source, and don't see any logic related to that idea in > ticket/web_ui.py where the feature is implemented.) > > > http://trac.edgewall.org/ticket/7562#comment:23 says that "there is no > longer a need for a specific option to unlink/link fields" but it's > not clear to me why that's the case. So it might be worth a feature > request. > The linked_fields would be a useful thing to me. > > > That said, is there a reason you want to use a "text" field instead of > a "select"? Some fields, like project numbers, contain non-numeric characters. So I made them text. Project numbers drop from the sky like rain. They need to be something one can enter in the ticket as needed. Is there a better option than text for this? > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
