Alec Thomas wrote:
Mmm, another thought...I think it would be useful to have ticket fields
Wiki formattable.

For example, I was messing around today with having an extra "virtual"
action "duplicate", which has a drop-down of tickets (although this
could just as easily be a free-form field). The action closes the ticket
and sets the custom field "duplicate" to the duplicate ticket number.
This is displayed in the summary but ideally it would be Wiki formatted
so you could just click on it.

So, question is whether to Wiki format all custom fields by default or
to have it as another optional flag for fields:

eg.

    [ticket-custom]
    duplicate = text
    duplicate.label = Duplicate of
    duplicate.wikify = true

To add some "weight" to the above ideas, here are some related tickets:

The duplicate field corresponds to ticket #1395
I had plans (+ an experimental implementation) on top of xref,
but please go ahead, I can always adapt to what you'll eventually do.

Wiki text for custom field is also proposed in ticket #1791
In addition to adding wiki format for custom field, this ticket
propose to add wiki formatting for the labels (idea which is
also proposed in ticket #925).

I'm all for these changes.
However, it *might* be interesting to be able to specify a "raw" text type.
After all, we already made that choice for the ticket summary (it's not
a wiki text field), so maybe it's worth being able to specify that some
text field is not a wiki text field.
I'd be in favor for the default text type to be "wiki", though.

-- Christian
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev

Reply via email to