Feature #1179
Optionally allow Text and Long Text custom fields support wiki formatting
| Status: | New | Start date: | 2008-05-05 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Custom fields | |||
| Target version: | - | |||
| Resolution: |
Description
It would be very helpful if Text and Long Text custom fields support wiki formatting. It would be even better if the wiki support can be activated or deactivated in a per-field basis, using a checkbox in the custom field properties (something like "Allow wiki format" next to the "Required" checkbox).
Related issues
History
#1 Updated by Arthaey Angosii almost 4 years ago
Implementing this would effectively make issue #1358 a duplicate of this by allowing me to have links in any custom field.
#2 Updated by Michael Burton over 2 years ago
#3 Updated by Jean-Baptiste Barth almost 2 years ago
Can you try the patch I proposed in #5794 and tell me if it works and fit your needs ?
#4 Updated by Leandro Lucarella almost 2 years ago
Jean-Baptiste Barth wrote:
Can you try the patch I proposed in #5794 and tell me if it works and fit your needs ?
I'm sorry, I don't have a Redmine instance to play with at the moment, but I took to the patches and, if I understand correctly what they do (bare in mind I'm not well versed in Ruby nor familiar with Redmine code), it's exactly what I wanted.
I prefer to have the option to textilize or not, but it wouldn't be too terrible if there is no option (it will not be backward compatible, though, and could cause some pain in people already using it as plain text).
Thanks!
#5 Updated by ju mar about 1 year ago
+1
I am also interested in having wiki-formatting in Text/Long Text custom fields. And I have a redmine install for testing purpose so I can test patches if needed.
#6 Updated by Andriy Lesyuk 5 months ago
I just have released Extended fields plugin which adds "Wiki text" custom field type... Please check.
#7 Updated by Maxim Nikolaevich 11 days ago
Guys,
I think long text custom field should be used as "description" field (i mean full support wiki syntax) and simple text field should not.
I believe it solves many issues related with this issue with simplest way - without any additional options