5 messages in com.mysql.lists.eventum-usersRE: Formatting of custom fields.| From | Sent On | Attachments |
|---|---|---|
| Eliot Blennerhassett | 11 Jul 2005 16:13 | |
| Joao Prado Maia | 11 Jul 2005 17:09 | |
| Eliot Blennerhassett | 13 Jul 2005 15:18 | |
| Joao Prado Maia | 13 Jul 2005 15:41 | |
| Eliot Blennerhassett | 13 Jul 2005 17:52 |
| Subject: | RE: Formatting of custom fields.![]() |
|---|---|
| From: | Eliot Blennerhassett (eble...@audioscience.com) |
| Date: | 07/13/2005 05:52:45 PM |
| List: | com.mysql.lists.eventum-users |
Thanks Joao
Eliot,
Both custom fields are textareas. But I think it happened with a textinput as well.
Well, I still have no idea how you got the names without double quotes around them,
My mistake, it is just the HTML <> that doesn't work.
but the HTML escaping bug is fixed on Bitkeeper and will be available on our next release.
Great.
[What we really wanted was to enable the customer fields without having a customer integration backend, instead filling them manually - I know this is not likely to be implemented though!]
I'm not sure what you mean here. The custom fields that you created are exactly what you are referring to above -- customers fields that don't require the customer integration stuff.
Well, when customer integration is turned on, there are extra fields in the issue entry screen. "Customer Details"
Eventum "understands" these better than custom fields. Eg. The quick search gets a 'Customer name' box, there is a separate customer column in the search results etc.
So I'm talking about enabling the existence, creation of users with Role=Customer without having the Customer integration backend.
But I have read the archives and know that this is unlikely to happen to the standard Eventum distribution.
Did I misunderstand something here?
--Joao
-- Eliot Blennerhassett *:-{)> AudioScience, Inc.




