##// END OF EJS Templates
Added automatic table of content support on wiki pages, based on h1., h2. and h3. headings....
Added automatic table of content support on wiki pages, based on h1., h2. and h3. headings. To display the page TOC, insert a line with this tag: {{toc}} or {{<toc}} => left aligned toc {{>toc}} => right aligned toc git-svn-id: http://redmine.rubyforge.org/svn/trunk@718 e93f8b46-1217-0410-a6f0-8f06a7374b81

File last commit:

r586:1cb5fc747f10
r707:f3364b9dce6f
Show More
ch01s05.html
2 lines | 4.5 KiB | text/html | HtmlLexer
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>5.&nbsp;Custom fields</title><link rel="stylesheet" href="html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.70.1"><link rel="start" href="index.html" title="Documentation"><link rel="up" href="ch01.html" title="Chapter&nbsp;1.&nbsp;Administration"><link rel="prev" href="ch01s04.html" title="4.&nbsp;Trackers"><link rel="next" href="ch01s06.html" title="6.&nbsp;Issue status"></head><body><a href="http://redmine.rubyforge.org/"><img src="../redmine.png" alt="redmine"></a><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.&nbsp;Custom fields</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s04.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;1.&nbsp;Administration</th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ch01s06.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e160"></a>5.&nbsp;Custom fields</h2></div></div></div><p>Custom fields allow you to add additional information in Projects, Issues or Users. A custom field can be of one the following types:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="guilabel">Integer</span> : positive or negative number</p></li><li><p><span class="guilabel">String</span> : a string of characters - one single line of input.</p></li><li><p><span class="guilabel">Text</span> : a string of characters with multiple lines of input. Differs from String Format by providing multiple lines of input instead of a single line.</p></li><li><p><span class="guilabel">Date</span> : date</p></li><li><p><span class="guilabel">Boolean</span> : true or false (check if necessary)</p></li><li><p><span class="guilabel">List</span> : value to select from a predefined list (aka: scroll list or select box)</p></li></ul></div><p>Validation elements can be defined:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="guilabel">Required</span> : A required field must have input in the forms</p></li><li><p><span class="guilabel">For all the projects</span> : field automatically associated to all of the projects</p></li><li><p><span class="guilabel">Min - max length</span> : minimum and maximum length for the input fields (0 means that there is no restriction)</p></li><li><p><span class="guilabel">Regular Expression</span> : regular expressions may provide validation of the input value</p><p>Examples:</p><p><code class="code">^\[A-Z]{4}\d+$</code> : 4 capital letters followed by one or several digits</p><p><code class="code">^[^0-9]*$</code> : characters only - no digits</p></li><li><p><span class="guilabel">Possible values</span> : possible values for the fields of "List" type. Values are separated by the character |</p></li></ul></div><p></p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e235"></a>5.1.&nbsp;Fields for Projects</h3></div></div></div><p></p><div class="itemizedlist"><ul type="disc"><li><p><span class="guilabel">Required</span> : required field</p></li></ul></div><p></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e246"></a>5.2.&nbsp;Fields for Issues</h3></div></div></div><p></p><div class="itemizedlist"><ul type="disc"><li><p><span class="guilabel">For all projects</span> : field automatically associated to all project Issues</p><p>If this option is not activated, each project could choose whether or not to use the field for its Issues (please see the project configuration).</p></li></ul></div><p></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e259"></a>5.3.&nbsp;Field for Users</h3></div></div></div><p></p><div class="itemizedlist"><ul type="disc"><li><p><span class="guilabel">Required</span> : required field</p></li></ul></div><p></p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s04.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ch01s06.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.&nbsp;Trackers&nbsp;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;6.&nbsp;Issue status</td></tr></table></div></body></html>