Edgewall Software

Changes between Initial Version and Version 1 of Ticket #11530


Ignore:
Timestamp:
Mar 10, 2014, 4:23:48 PM (10 years ago)
Author:
Ryan J Ollos
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11530 – Description

    initial v1  
    11Two issues were discussed on the [https://groups.google.com/d/msg/trac-users/lWB2c3U3TtM/IpK3ziT3zPcJ mailing list]:
    2  1. It should be documented that lines need to be preceded by whitespace to have a multi-line ticket description. For example,
     2 1. It should be documented that lines 2:end need to be indented with whitespace to have a multi-line ticket description. For example,
    33{{{#!ini
    44[ticket]
    … …  
    1010 This would be applicable to any `textarea`. Description is currently the only one in `[ticket]` section (TracIni#ticket-section), but we may also need to consider the `value` parameter of `textarea` custom fields (TracTicketsCustomFields#AvailableFieldTypesandOptions).
    1111
    12  2. `ConfigParser` in Python 2.x does not appear to support empty lines. The empty lines are stripped out. We'll need a workaround such as specifying empty lines with a single `\` character, and then stripping out the characters from the empty lines before rendering the ticket description.
     12 2. Empty lines can't be included in the `[ticket] default_description` because `ConfigParser` in Python 2.x does not appear to support empty lines. The empty lines are stripped out. We'll need a workaround such as specifying empty lines with a single `\` character, and then stripping out the character before rendering an empty line in the ticket description.