Redmine

Implementing this would effectively make issue #1358 a duplicate of this by allowing me to have links in any custom field.

Related issues: #1358, #2906

Can you try the patch I proposed in #5794 and tell me if it works and fit your needs ?

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!

+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.

I just have released Extended fields plugin which adds "Wiki text" custom field type... Please check.

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

+1 for this feature :)

Hi i use fix on my redmine:
I use Redmine::WikiFormatting.to_html for "text" custom field.

./app/helper/issue_helper.rb

def render_custom_fields_rows(issue)
return if issue.custom_field_values.empty?
ordered_values = []
half = (issue.custom_field_values.size / 2.0).ceil
half.times do |i|
ordered_values << issue.custom_field_values[i]
ordered_values << issue.custom_field_values[i + half]
end
s = "<tr>\n"
n = 0
ordered_values.compact.each do |value|
s << "</tr>\n<tr>\n" if n > 0 && (n % 2) == 0
s << "\t<th>#{ h(value.custom_field.name) }:</th><td>#{ show_value(value) }</td>\n"
n += 1
end
s << "</tr>\n"
s.html_safe
end


./lib/redmine/custom_field_format.rb

def format_as_text(value)
Redmine::WikiFormatting.to_html(Setting.text_formatting, value.to_s)
end

['string','int','float','list'].each do |name|
define_method("format_as_#{name}") {|value| return value}
end

Andriy Lesyuk wrote:

I just have released Extended fields plugin which adds "Wiki text" custom field type... Please check.

I personally use this plugin. However, there is a critical challenge I faced which didn't allow me to use it fully. The 'Wiki text' is a new type of field and fields types are not changeable AFTER they are created. so long text fields which we have already created cann't take the benefit of this. I know I could tinker DB - but want to avoid this.

Add Related #13588.

Maxim Nikolaevich wrote:

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

I just wanna show pic about extra options: http://verkoren.wordpress.com/2012/04/07/your-companys-app-vs-typical-apple-and-google-products/
Guys from team - i can do patch to extend long text with full wiki support - If you agree with me that this best solution

Other Related #202, #7067, #5250

Maxim Nikolaevich wrote:

I just wanna show pic about extra options: http://verkoren.wordpress.com/2012/04/07/your-companys-app-vs-typical-apple-and-google-products/
Guys from team - i can do patch to extend long text with full wiki support - If you agree with me that this best solution

Don't know what exactly was the connotation of the link you posted. Never-the-less, I think this is the essential feature that is quite desirable.

+100

Add related #5250, #7067

Dipan Mehta wrote:

Add related #5250, #7067

Done. Thanks for the hint.

Dipan Mehta wrote:

Andriy Lesyuk wrote:

I just have released Extended fields plugin which adds "Wiki text" custom field type... Please check.

I personally use this plugin. However, there is a critical challenge I faced which didn't allow me to use it fully. The 'Wiki text' is a new type of field and fields types are not changeable AFTER they are created. so long text fields which we have already created cann't take the benefit of this. I know I could tinker DB - but want to avoid this.

The other issue I have with this is that the wikitext field is still in the column layout, so an H1 or H2 gets wrapped, and I found it wasn't very useful. I wanted to use it as a place to keep test cases for our QA people, but it's so unwieldy at the moment, I'll stick with using the description field.

I think what I'm looking for is more of a secondary description field. Somewhere I can put nicely formatted text for test cases that doesn't require me to update the description or get lost in the Notes.

+100 for this feature, this feature would be awesome. I'm also trying to use long text fields to put Test Cases in (its a required field so we don't forget!), and the formatting of this field would really help

Will this allow existing text fields to get text formatting? or will it be applicable on new fields taken only?

The option is available for existing or new custom fields.

Which checkin is this change implemented in?

Sorry if this is not the place to post but I can't see this feature having correctly been implemented in Redmine (old or latest versions).

When I create a long text custom field, I click on the check box "Text formatting", but when used in a tracker the field doesn't show the text formatting icons above.

Any help would be appreciated.

Thanks!

Luis Blasco wrote:

When I create a long text custom field, I click on the check box "Text formatting", but when used in a tracker the field doesn't show the text formatting icons above.

What do you mean "icons"?

Luis Blasco wrote:

Actually I meant the formatting buttons above the text field.

Please create new issue for request.

Done. Thank you.

FTR: #21924