EsRedmineSettings » History » Version 9
Leonel Iturralde, 2015-03-31 21:24
1 | 1 | Juan Carlos Sabastizagal | h1. Configuración |
---|---|---|---|
2 | 1 | Juan Carlos Sabastizagal | |
3 | 1 | Juan Carlos Sabastizagal | {{>TOC}} |
4 | 1 | Juan Carlos Sabastizagal | |
5 | 1 | Juan Carlos Sabastizagal | h2. Configuración General |
6 | 1 | Juan Carlos Sabastizagal | |
7 | 1 | Juan Carlos Sabastizagal | h3. Título de la aplicación |
8 | 1 | Juan Carlos Sabastizagal | |
9 | 2 | Leonel Iturralde | Título que aparece en la cabecera de la aplicación. Este es el enlace justo debajo de la barra de título con « Home/My page/Projects/Help» cuando esta logeado. |
10 | 1 | Juan Carlos Sabastizagal | |
11 | 3 | Leonel Iturralde | h3. Texto de Bienvenida |
12 | 1 | Juan Carlos Sabastizagal | |
13 | 3 | Leonel Iturralde | Texto mostrado en la página principal de Redmine. Este texto puede contener etiquetas HTML. |
14 | 1 | Juan Carlos Sabastizagal | |
15 | 4 | Leonel Iturralde | h3. Tamaño Máximo de Adjunto |
16 | 1 | Juan Carlos Sabastizagal | |
17 | 6 | Leonel Iturralde | Tamaño máximo de archivos subidos (en "kibi-bytes":http://en.wikipedia.org/wiki/Binary_prefix). _Por defecto: 5120 (5 "mebi-bytes":http://en.wikipedia.org/wiki/Binary_prefix )_ |
18 | 1 | Juan Carlos Sabastizagal | |
19 | 5 | Leonel Iturralde | h3. Objetos por página |
20 | 1 | Juan Carlos Sabastizagal | |
21 | 5 | Leonel Iturralde | Aquí puedes configurar los valores fijos que los usuarios pueden seleccionar para la cantidad de objectos (peticiones, revisiones, etc.) |
22 | 1 | Juan Carlos Sabastizagal | |
23 | 5 | Leonel Iturralde | _Por Defecto: 25, 50, 100_ |
24 | 1 | Juan Carlos Sabastizagal | |
25 | 7 | Leonel Iturralde | h3. Días a mostrar en la actividad de proyecto |
26 | 1 | Juan Carlos Sabastizagal | |
27 | 7 | Leonel Iturralde | El valor inicial (y recurrente mientras navegas) de la cantidad de días que la actividad(es) del proyecto es mostrada en [[EsRedmineProjectActivity|activity]]-tab. |
28 | 1 | Juan Carlos Sabastizagal | |
29 | 8 | Leonel Iturralde | h3. Nombre y Ruta del Servidor |
30 | 1 | Juan Carlos Sabastizagal | |
31 | 8 | Leonel Iturralde | Nombre y Ruta del Servidor de Redmine. Este nombre es utilizado para escribir URL en correo electronicos enviados a usuarios. Ejemplo nombre del servidor de este redmine es redmine.org. |
32 | 1 | Juan Carlos Sabastizagal | |
33 | 9 | Leonel Iturralde | h3. Protocolo |
34 | 1 | Juan Carlos Sabastizagal | |
35 | 9 | Leonel Iturralde | Protocolo usado para generar enlaces en notificaciones de correo electrónicos. _Por Defecto: http_ |
36 | 1 | Juan Carlos Sabastizagal | |
37 | 9 | Leonel Iturralde | Enlaces en correo electrónicos son "adivinados", pero no puede determinarse si estás usando un servidor web inseguro (http) or seguro (https -> http sobre SSL). |
38 | 1 | Juan Carlos Sabastizagal | |
39 | 1 | Juan Carlos Sabastizagal | h3. Text formatting |
40 | 1 | Juan Carlos Sabastizagal | |
41 | 1 | Juan Carlos Sabastizagal | Formatting method applied to the "description" fields of the issues, news, documents... |
42 | 1 | Juan Carlos Sabastizagal | |
43 | 1 | Juan Carlos Sabastizagal | h3. Cache formatted text (1.0) |
44 | 1 | Juan Carlos Sabastizagal | |
45 | 1 | Juan Carlos Sabastizagal | Text formatting tranforms raw text to HTML and runs each time a formatted text is sent to the browser (eg. issue description, wiki page...). This process can be slow on large texts. |
46 | 1 | Juan Carlos Sabastizagal | |
47 | 1 | Juan Carlos Sabastizagal | This setting lets you enable caching of formatted text. Cached text is stored in a cache store that can be configured with @config.action_controller.cache_store@. By default, this cache store is "MemoryStore":http://api.rubyonrails.org/classes/ActiveSupport/Cache/MemoryStore.html. |
48 | 1 | Juan Carlos Sabastizagal | |
49 | 1 | Juan Carlos Sabastizagal | If you need to enable caching, it's highly recommended that you configure the cache to use another cache store like MemCacheStore or FileStore if memory is a concern. |
50 | 1 | Juan Carlos Sabastizagal | |
51 | 1 | Juan Carlos Sabastizagal | You can read more about cache stores in the Rails guides: |
52 | 1 | Juan Carlos Sabastizagal | http://guides.rubyonrails.org/caching_with_rails.html#cache-stores |
53 | 1 | Juan Carlos Sabastizagal | |
54 | 1 | Juan Carlos Sabastizagal | h3. Wiki history compression |
55 | 1 | Juan Carlos Sabastizagal | |
56 | 1 | Juan Carlos Sabastizagal | Lets you activate compression for wiki history storage (reduces database size). _Default: disabled_ |
57 | 1 | Juan Carlos Sabastizagal | |
58 | 1 | Juan Carlos Sabastizagal | h3. Feed content limit |
59 | 1 | Juan Carlos Sabastizagal | |
60 | 1 | Juan Carlos Sabastizagal | Maximum number of records contained in RSS feeds. _Default: 15_ |
61 | 1 | Juan Carlos Sabastizagal | |
62 | 1 | Juan Carlos Sabastizagal | h3. Max size of text files displayed inline KB |
63 | 1 | Juan Carlos Sabastizagal | |
64 | 1 | Juan Carlos Sabastizagal | It provides a way to limit the maximum size of text files which are display inline. |
65 | 1 | Juan Carlos Sabastizagal | |
66 | 1 | Juan Carlos Sabastizagal | h3. Max number of diff lines displayed |
67 | 1 | Juan Carlos Sabastizagal | |
68 | 1 | Juan Carlos Sabastizagal | It provides a way to limit the maximum number of diff lines which are displayed by Redmine. |
69 | 1 | Juan Carlos Sabastizagal | |
70 | 1 | Juan Carlos Sabastizagal | h2. Display |
71 | 1 | Juan Carlos Sabastizagal | |
72 | 1 | Juan Carlos Sabastizagal | h3. Theme |
73 | 1 | Juan Carlos Sabastizagal | |
74 | 1 | Juan Carlos Sabastizagal | This option lets you choose a custom theme. |
75 | 1 | Juan Carlos Sabastizagal | Redmine is shipped with two additional themes besides the [[ThemeDefault|default]] theme: |
76 | 1 | Juan Carlos Sabastizagal | * [[ThemeAlternate|alternate]], which mainly provides issue list colorization based on issues priority. |
77 | 1 | Juan Carlos Sabastizagal | * [[ThemeClassic|classic]], which is derived from the Redmine 0.5.1 design and brings a _classic_ look. |
78 | 1 | Juan Carlos Sabastizagal | |
79 | 1 | Juan Carlos Sabastizagal | Screenshot of the [[ThemeAlternate|alternate]] theme: |
80 | 1 | Juan Carlos Sabastizagal | |
81 | 1 | Juan Carlos Sabastizagal | !alternate_theme.png! |
82 | 1 | Juan Carlos Sabastizagal | |
83 | 1 | Juan Carlos Sabastizagal | Themes are located in @public/themes/@. You can read more about [[Themes]]. |
84 | 1 | Juan Carlos Sabastizagal | |
85 | 1 | Juan Carlos Sabastizagal | h3. Default language |
86 | 1 | Juan Carlos Sabastizagal | |
87 | 1 | Juan Carlos Sabastizagal | The default language is selected when the application could not determine the user's browser language. The default language is also used when sending email to multiple users. _Default: English_ |
88 | 1 | Juan Carlos Sabastizagal | |
89 | 1 | Juan Carlos Sabastizagal | h3. Date format |
90 | 1 | Juan Carlos Sabastizagal | |
91 | 1 | Juan Carlos Sabastizagal | Lets you choose how dates are displayed: |
92 | 1 | Juan Carlos Sabastizagal | |
93 | 1 | Juan Carlos Sabastizagal | * *Based on user's language*: dates will be displayed specifically for each user, according to the format defined for its language |
94 | 1 | Juan Carlos Sabastizagal | * *Other formats*: dates will always be displayed using the specified format |
95 | 1 | Juan Carlos Sabastizagal | |
96 | 1 | Juan Carlos Sabastizagal | _Default: Based on user's language_ |
97 | 1 | Juan Carlos Sabastizagal | |
98 | 1 | Juan Carlos Sabastizagal | h3. Time format |
99 | 1 | Juan Carlos Sabastizagal | |
100 | 1 | Juan Carlos Sabastizagal | Lets you choose how times are displayed: |
101 | 1 | Juan Carlos Sabastizagal | |
102 | 1 | Juan Carlos Sabastizagal | * *Based on user's language*: times will be displayed specifically for each user, according to the format defined for its language |
103 | 1 | Juan Carlos Sabastizagal | * *Other formats*: times will always be displayed using the specified format |
104 | 1 | Juan Carlos Sabastizagal | |
105 | 1 | Juan Carlos Sabastizagal | _Default: Based on user's language_ |
106 | 1 | Juan Carlos Sabastizagal | |
107 | 1 | Juan Carlos Sabastizagal | h3. Users display format |
108 | 1 | Juan Carlos Sabastizagal | |
109 | 1 | Juan Carlos Sabastizagal | Lets you choose how usernames are displayed. The following combinations are provided: |
110 | 1 | Juan Carlos Sabastizagal | |
111 | 1 | Juan Carlos Sabastizagal | * _Firstname_ |
112 | 1 | Juan Carlos Sabastizagal | * _Firstname Surname_ |
113 | 1 | Juan Carlos Sabastizagal | * _Surname Firstname_ |
114 | 1 | Juan Carlos Sabastizagal | * _Surname, Firstname_ |
115 | 1 | Juan Carlos Sabastizagal | * _Username_ |
116 | 1 | Juan Carlos Sabastizagal | |
117 | 1 | Juan Carlos Sabastizagal | h3. Use Gravatar user icons |
118 | 1 | Juan Carlos Sabastizagal | |
119 | 1 | Juan Carlos Sabastizagal | If enabled, users "Gravatars":http://en.gravatar.com/ (globally recognized avatar) will be displayed in several places. |
120 | 1 | Juan Carlos Sabastizagal | |
121 | 1 | Juan Carlos Sabastizagal | h3. Default Gravatar image |
122 | 1 | Juan Carlos Sabastizagal | |
123 | 1 | Juan Carlos Sabastizagal | The image to use for users who don't have a Gravatar. |
124 | 1 | Juan Carlos Sabastizagal | |
125 | 1 | Juan Carlos Sabastizagal | h2. Authentication |
126 | 1 | Juan Carlos Sabastizagal | |
127 | 1 | Juan Carlos Sabastizagal | h3. Authentication required |
128 | 1 | Juan Carlos Sabastizagal | |
129 | 1 | Juan Carlos Sabastizagal | If this option is checked, no page of the application is accessible to anonymous users. Users must sign to access the application. _Default: No_ |
130 | 1 | Juan Carlos Sabastizagal | |
131 | 1 | Juan Carlos Sabastizagal | h3. Autologin |
132 | 1 | Juan Carlos Sabastizagal | |
133 | 1 | Juan Carlos Sabastizagal | This option let users use the auto-login feature. _Default: Disabled_ |
134 | 1 | Juan Carlos Sabastizagal | |
135 | 1 | Juan Carlos Sabastizagal | h3. Self-registration |
136 | 1 | Juan Carlos Sabastizagal | |
137 | 1 | Juan Carlos Sabastizagal | This option lets you enable/disable new users self registration: |
138 | 1 | Juan Carlos Sabastizagal | |
139 | 1 | Juan Carlos Sabastizagal | * *disabled*: users are not allowed to register |
140 | 1 | Juan Carlos Sabastizagal | * *account activation by email*: new users receive an email containing a link used to activate their accounts (users must provide a valid email address). |
141 | 1 | Juan Carlos Sabastizagal | * *manual account activation* _(default)_: new users' accounts are created but need administrator approval. Administrators receive an email informing them that an account is pending their approval. |
142 | 1 | Juan Carlos Sabastizagal | * *automatic account activation*: new users can log in as soon as they have registered. |
143 | 1 | Juan Carlos Sabastizagal | |
144 | 1 | Juan Carlos Sabastizagal | h3. Minimum password length |
145 | 1 | Juan Carlos Sabastizagal | |
146 | 1 | Juan Carlos Sabastizagal | Let's the admin decide on the minimum length of the chosen passwords. |
147 | 1 | Juan Carlos Sabastizagal | |
148 | 1 | Juan Carlos Sabastizagal | _Default: 4_ |
149 | 1 | Juan Carlos Sabastizagal | |
150 | 1 | Juan Carlos Sabastizagal | h3. Lost password |
151 | 1 | Juan Carlos Sabastizagal | |
152 | 1 | Juan Carlos Sabastizagal | If this option is checked, lost password functionality is available. _Default: Yes_ |
153 | 1 | Juan Carlos Sabastizagal | |
154 | 1 | Juan Carlos Sabastizagal | h3. Allow OpenID login and registration |
155 | 1 | Juan Carlos Sabastizagal | |
156 | 1 | Juan Carlos Sabastizagal | Provides the admin a way to disable OpenID logins and registrations. |
157 | 1 | Juan Carlos Sabastizagal | Note that the setting is immutable as long as the dependency for the feature (an installed copy of the @ruby-openid@ gem) is not met. You can simply install it using @gem install ruby-openid@. |
158 | 1 | Juan Carlos Sabastizagal | |
159 | 1 | Juan Carlos Sabastizagal | h2. Projects |
160 | 1 | Juan Carlos Sabastizagal | |
161 | 1 | Juan Carlos Sabastizagal | h3. New projects are public by default |
162 | 1 | Juan Carlos Sabastizagal | |
163 | 1 | Juan Carlos Sabastizagal | The default state of newly created projects. The project can still be made non-public while creating new project or after the creation of the project. |
164 | 1 | Juan Carlos Sabastizagal | |
165 | 1 | Juan Carlos Sabastizagal | h3. Generate sequential project identifiers |
166 | 1 | Juan Carlos Sabastizagal | |
167 | 1 | Juan Carlos Sabastizagal | This setting will let Redmine propose sequential project identifiers for you. This can still be manually changed only while creating the project, not afterward. |
168 | 1 | Juan Carlos Sabastizagal | |
169 | 1 | Juan Carlos Sabastizagal | h3. Role given to a non-admin user who creates a project |
170 | 1 | Juan Carlos Sabastizagal | |
171 | 1 | Juan Carlos Sabastizagal | Defines which role is given by default to a non-admin user who creates a project (this only applies when you have configured Redmine permissions in such a way that non-admin users are actually privileged to create projects). |
172 | 1 | Juan Carlos Sabastizagal | |
173 | 1 | Juan Carlos Sabastizagal | h2. Issue tracking |
174 | 1 | Juan Carlos Sabastizagal | |
175 | 1 | Juan Carlos Sabastizagal | h3. Allow cross-project issue relations |
176 | 1 | Juan Carlos Sabastizagal | |
177 | 1 | Juan Carlos Sabastizagal | If set to true, relations between issues from different projects can be created. _Default: No_ |
178 | 1 | Juan Carlos Sabastizagal | |
179 | 1 | Juan Carlos Sabastizagal | h3. Display subprojects issues on main projects by default |
180 | 1 | Juan Carlos Sabastizagal | |
181 | 1 | Juan Carlos Sabastizagal | If set to true, subprojects issues will be displayed by default on the issue list, calendar and gantt of the main projects (Since r1198). _Default: Yes_ |
182 | 1 | Juan Carlos Sabastizagal | |
183 | 1 | Juan Carlos Sabastizagal | h3. Calculate the issue done ratio |
184 | 1 | Juan Carlos Sabastizagal | |
185 | 1 | Juan Carlos Sabastizagal | Defines how the Issue Done Percentage is set. |
186 | 1 | Juan Carlos Sabastizagal | |
187 | 1 | Juan Carlos Sabastizagal | * *Use the issue field* _(default)_: Users can manually set % done. |
188 | 1 | Juan Carlos Sabastizagal | * *Use the issue status*: Each issue status can be assigned a percentage. This enables the [[RedmineIssueTrackingSetup#-Done|"% Done" option for issues]] and the [[RedmineIssueTrackingSetup#Update-issue-done-ratios|"Update issue done ratios" command in the issue statuses overview]]. |
189 | 1 | Juan Carlos Sabastizagal | |
190 | 1 | Juan Carlos Sabastizagal | h3. Issues export limit |
191 | 1 | Juan Carlos Sabastizagal | |
192 | 1 | Juan Carlos Sabastizagal | Maximum number of issues contained in CSV and PDF exports. _Default: 500_ |
193 | 1 | Juan Carlos Sabastizagal | |
194 | 1 | Juan Carlos Sabastizagal | h3. Default columns displayed on the issue list |
195 | 1 | Juan Carlos Sabastizagal | |
196 | 1 | Juan Carlos Sabastizagal | This setting lets you define which columns are displayed on the issue lists by default. |
197 | 1 | Juan Carlos Sabastizagal | Only custom fields that are marked as 'For all projects' can be selected here. |
198 | 1 | Juan Carlos Sabastizagal | |
199 | 1 | Juan Carlos Sabastizagal | h2. Email notifications |
200 | 1 | Juan Carlos Sabastizagal | |
201 | 1 | Juan Carlos Sabastizagal | h3. Emission mail address |
202 | 1 | Juan Carlos Sabastizagal | |
203 | 1 | Juan Carlos Sabastizagal | Email address used in the "From" field of messages sent to users. |
204 | 1 | Juan Carlos Sabastizagal | |
205 | 1 | Juan Carlos Sabastizagal | h3. Blind carbon copy recipients (bcc) |
206 | 1 | Juan Carlos Sabastizagal | |
207 | 1 | Juan Carlos Sabastizagal | If set to true, email notification will be sent as Blind carbon copy. _Default: Yes_ |
208 | 1 | Juan Carlos Sabastizagal | |
209 | 1 | Juan Carlos Sabastizagal | h3. Plain text mail |
210 | 1 | Juan Carlos Sabastizagal | |
211 | 1 | Juan Carlos Sabastizagal | If set to true, emails are sent in plain text only (no HTML). |
212 | 1 | Juan Carlos Sabastizagal | |
213 | 1 | Juan Carlos Sabastizagal | h3. Emails footer |
214 | 1 | Juan Carlos Sabastizagal | |
215 | 1 | Juan Carlos Sabastizagal | Here you can enter some text that will be appended to the emails sent by the application. |
216 | 1 | Juan Carlos Sabastizagal | |
217 | 1 | Juan Carlos Sabastizagal | h2. Incoming emails |
218 | 1 | Juan Carlos Sabastizagal | |
219 | 1 | Juan Carlos Sabastizagal | See for detailed instructions about these settings [[RedmineReceivingEmails]]. |
220 | 1 | Juan Carlos Sabastizagal | |
221 | 1 | Juan Carlos Sabastizagal | h3. Truncate emails after one of these lines |
222 | 1 | Juan Carlos Sabastizagal | |
223 | 1 | Juan Carlos Sabastizagal | These setting can be used to remove signatures from incoming emails. |
224 | 1 | Juan Carlos Sabastizagal | |
225 | 1 | Juan Carlos Sabastizagal | h3. Enable WS for incoming emails |
226 | 1 | Juan Carlos Sabastizagal | |
227 | 1 | Juan Carlos Sabastizagal | Redmine can be configured to allow issue creation or comments via email. In order to use that feature, you have to enable the API that receives emails. That is where this setting is for. _Default: Off_ |
228 | 1 | Juan Carlos Sabastizagal | |
229 | 1 | Juan Carlos Sabastizagal | h3. API key |
230 | 1 | Juan Carlos Sabastizagal | |
231 | 1 | Juan Carlos Sabastizagal | Within this setting you can enter a secret key used for the issue creation or comments via email feature. |
232 | 1 | Juan Carlos Sabastizagal | |
233 | 1 | Juan Carlos Sabastizagal | h2. Repositories |
234 | 1 | Juan Carlos Sabastizagal | |
235 | 1 | Juan Carlos Sabastizagal | h3. Autofetch commits |
236 | 1 | Juan Carlos Sabastizagal | |
237 | 1 | Juan Carlos Sabastizagal | If this option is activated, the application automatically retrieves the new revisions when a user consults the repository. |
238 | 1 | Juan Carlos Sabastizagal | |
239 | 1 | Juan Carlos Sabastizagal | _Default: Yes_ |
240 | 1 | Juan Carlos Sabastizagal | |
241 | 1 | Juan Carlos Sabastizagal | You can disable this option and automate the call to Repository#fetch_changesets using cron to regularly retrieve the revisions for all of the repositories in the background. |
242 | 1 | Juan Carlos Sabastizagal | Example: |
243 | 1 | Juan Carlos Sabastizagal | <pre>ruby script/runner "Repository.fetch_changesets" -e production</pre> |
244 | 1 | Juan Carlos Sabastizagal | |
245 | 1 | Juan Carlos Sabastizagal | You can also call this task from your repository in a post-commit or post-receive hook, so that changesets are fetched after each commit. |
246 | 1 | Juan Carlos Sabastizagal | Here is a tutorial for doing so with git: http://finalcog.com/remine-git-post-receive |
247 | 1 | Juan Carlos Sabastizagal | |
248 | 1 | Juan Carlos Sabastizagal | h3. Enable WS for repository management |
249 | 1 | Juan Carlos Sabastizagal | |
250 | 1 | Juan Carlos Sabastizagal | This option should be activated only if you installed the script for automatic SVN repository creation. _Default: No_ |
251 | 1 | Juan Carlos Sabastizagal | |
252 | 1 | Juan Carlos Sabastizagal | h3. Enabled SCM |
253 | 1 | Juan Carlos Sabastizagal | |
254 | 1 | Juan Carlos Sabastizagal | Here you can (de)select the SCM-systems Redmine should "provide" to the individual projects. This setting is useful if you only support several SCM-systems (e.g. only Git or only SVN). |
255 | 1 | Juan Carlos Sabastizagal | |
256 | 1 | Juan Carlos Sabastizagal | h3. Repositories encodings |
257 | 1 | Juan Carlos Sabastizagal | |
258 | 1 | Juan Carlos Sabastizagal | This option lets you specify preferred encodings for repository files (multiple values allowed, comma separated). These encodings are used to convert files content and diff to UTF-8 so that they're properly displayed in the browser. |
259 | 1 | Juan Carlos Sabastizagal | When entering multiple encodings, the first valid encoding regarding the file content is used. |
260 | 1 | Juan Carlos Sabastizagal | |
261 | 1 | Juan Carlos Sabastizagal | For French users, this option can be for example set to: |
262 | 1 | Juan Carlos Sabastizagal | |
263 | 1 | Juan Carlos Sabastizagal | UTF-8, ISO 8859-15, CP1252 |
264 | 1 | Juan Carlos Sabastizagal | |
265 | 1 | Juan Carlos Sabastizagal | For Japanese users: |
266 | 1 | Juan Carlos Sabastizagal | |
267 | 1 | Juan Carlos Sabastizagal | ISO-2022-JP, EUC-JP, UTF-8, SHIF_JIS, WINDOWS-31J |
268 | 1 | Juan Carlos Sabastizagal | |
269 | 1 | Juan Carlos Sabastizagal | h3. Maximum number of revisions displayed on file log |
270 | 1 | Juan Carlos Sabastizagal | |
271 | 1 | Juan Carlos Sabastizagal | It provides a way to limit the amount of revisions which are retrieved from the SCM for a certain, browsed path. |
272 | 1 | Juan Carlos Sabastizagal | |
273 | 1 | Juan Carlos Sabastizagal | h3. Referencing issues in commit messages |
274 | 1 | Juan Carlos Sabastizagal | |
275 | 1 | Juan Carlos Sabastizagal | When fetched from the repositories, commit messages are scanned for referenced or fixed issue IDs. |
276 | 1 | Juan Carlos Sabastizagal | These options lets you define keywords that can be used in commit message to reference or fix issues automatically, and the status to apply to fixed issues. |
277 | 1 | Juan Carlos Sabastizagal | |
278 | 1 | Juan Carlos Sabastizagal | Default keywords are: |
279 | 1 | Juan Carlos Sabastizagal | |
280 | 1 | Juan Carlos Sabastizagal | * for referencing issues: refs, references, IssueID |
281 | 1 | Juan Carlos Sabastizagal | * for fixing issues: fixes, closes |
282 | 1 | Juan Carlos Sabastizagal | |
283 | 1 | Juan Carlos Sabastizagal | There's no default status defined for fixed issue. You'll have to specify it if you want to enable auto closure of issues. |
284 | 1 | Juan Carlos Sabastizagal | If you want to reference issues without using keywords, enter a single star: * in the *Referencing keywords* (Administration/Repository) setting. In this case, any issue ID found in the message will be linked to the changeset. |
285 | 1 | Juan Carlos Sabastizagal | |
286 | 1 | Juan Carlos Sabastizagal | Example of a working commit message using default keywords: |
287 | 1 | Juan Carlos Sabastizagal | |
288 | 1 | Juan Carlos Sabastizagal | This commit refs #1, #2 and fixes #3 |
289 | 1 | Juan Carlos Sabastizagal | |
290 | 1 | Juan Carlos Sabastizagal | This message would reference issues 1 and 2 and automatically fix issue 3. |
291 | 1 | Juan Carlos Sabastizagal | After a keyword issue IDs can be separated with a space, a comma or &. |