RedmineSettings » History » Version 43

Ben Blanco, 2016-01-05 10:44

1 1 Jean-Philippe Lang
h1. Application Settings
2 1 Jean-Philippe Lang
3 3 Jean-Philippe Lang
{{>TOC}}
4 1 Jean-Philippe Lang
5 3 Jean-Philippe Lang
h2. General settings
6 3 Jean-Philippe Lang
7 3 Jean-Philippe Lang
h3. Application title
8 3 Jean-Philippe Lang
9 17 Thomas Lecavelier
Title which appears in heading of the application. This is the link just under the little bar with « Home/My page/Projects/Help» when you're logged in.
10 1 Jean-Philippe Lang
11 3 Jean-Philippe Lang
h3. Welcome text
12 1 Jean-Philippe Lang
13 17 Thomas Lecavelier
Text displayed on the home page of Redmine. This text can contain HTML tags.
14 1 Jean-Philippe Lang
15 22 Jean-Philippe Lang
h3. Attachment max. size
16 22 Jean-Philippe Lang
17 22 Jean-Philippe Lang
Maximum size of uploaded files (in "kibi-bytes":http://en.wikipedia.org/wiki/Binary_prefix). _Default: 5120 (i.e. 5 "mebi-bytes":http://en.wikipedia.org/wiki/Binary_prefix )_
18 22 Jean-Philippe Lang
19 22 Jean-Philippe Lang
h3. Objects per page options
20 22 Jean-Philippe Lang
21 22 Jean-Philippe Lang
Here you can configure the fixed values which users can select for the amount of objects (issues, commits etc.) which are displayed per page.
22 22 Jean-Philippe Lang
23 22 Jean-Philippe Lang
_Default: 25, 50, 100_
24 22 Jean-Philippe Lang
25 22 Jean-Philippe Lang
h3. Days displayed on project activity
26 22 Jean-Philippe Lang
27 22 Jean-Philippe Lang
The initial (and recurring while browsing) amount of days of which the project(s)-activity is shown in the [[RedmineProjectActivity|activity]]-tab.
28 22 Jean-Philippe Lang
29 23 Jean-Philippe Lang
h3. Host name and path
30 22 Jean-Philippe Lang
31 23 Jean-Philippe Lang
Host name and path of your redmine server. This name is used to write URL in emails sent to users. i.e.: the hostname of this precise redmine is redmine.org.
32 22 Jean-Philippe Lang
33 22 Jean-Philippe Lang
h3. Protocol
34 22 Jean-Philippe Lang
35 22 Jean-Philippe Lang
Protocol used to generate links in email notifications. _Default: http_
36 22 Jean-Philippe Lang
37 22 Jean-Philippe Lang
Links in email are "guessed", but can't determine whether you're using an unsecure web server (http) or a secure one (https -> http over SSL).
38 22 Jean-Philippe Lang
39 22 Jean-Philippe Lang
h3. Text formatting
40 22 Jean-Philippe Lang
41 22 Jean-Philippe Lang
Formatting method applied to the "description" fields of the issues, news, documents...
42 22 Jean-Philippe Lang
43 24 Jean-Philippe Lang
h3. Cache formatted text (1.0)
44 24 Jean-Philippe Lang
45 43 Ben Blanco
Text formatting tranforms raw text to HTML and runs each time a formatted text is sent to a user's browser (eg. issue description, wiki page...), and this process can be slow with large pages or texts.
46 24 Jean-Philippe Lang
47 43 Ben Blanco
This setting lets you enable caching of formatted text.
48 1 Jean-Philippe Lang
49 43 Ben Blanco
In order to use this feature you also need to specify a cache store, such as @config.action_controller.cache_store = :memory_store@, which you configure by adding this setting to your @config/environments/production.rb@, for example:
50 43 Ben Blanco
51 43 Ben Blanco
<pre>
52 43 Ben Blanco
  config.consider_all_requests_local = false
53 43 Ben Blanco
  config.action_controller.perform_caching = true
54 43 Ben Blanco
55 43 Ben Blanco
  # Now here we specify which cache store we want redmine to use:
56 43 Ben Blanco
  config.action_controller.cache_store = :memory_store
57 43 Ben Blanco
</pre>
58 43 Ben Blanco
59 43 Ben Blanco
By default, this cache store is "MemoryStore":http://api.rubyonrails.org/classes/ActiveSupport/Cache/MemoryStore.html.
60 43 Ben Blanco
61 43 Ben Blanco
If RAM memory usage on your server is a concern, it's highly recommended that you configure the cache to use another cache store like MemCacheStore or FileStore.
62 24 Jean-Philippe Lang
63 24 Jean-Philippe Lang
You can read more about cache stores in the Rails guides:
64 24 Jean-Philippe Lang
http://guides.rubyonrails.org/caching_with_rails.html#cache-stores
65 24 Jean-Philippe Lang
66 22 Jean-Philippe Lang
h3. Wiki history compression
67 22 Jean-Philippe Lang
68 22 Jean-Philippe Lang
Lets you activate compression for wiki history storage (reduces database size). _Default: disabled_
69 22 Jean-Philippe Lang
70 22 Jean-Philippe Lang
h3. Feed content limit
71 22 Jean-Philippe Lang
72 1 Jean-Philippe Lang
Maximum number of records contained in RSS feeds. _Default: 15_
73 22 Jean-Philippe Lang
74 22 Jean-Philippe Lang
h3. Max size of text files displayed inline KB
75 1 Jean-Philippe Lang
76 23 Jean-Philippe Lang
It provides a way to limit the maximum size of text files which are display inline.
77 22 Jean-Philippe Lang
78 22 Jean-Philippe Lang
h3. Max number of diff lines displayed
79 22 Jean-Philippe Lang
80 23 Jean-Philippe Lang
It provides a way to limit the maximum number of diff lines which are displayed by Redmine.
81 22 Jean-Philippe Lang
82 22 Jean-Philippe Lang
h2. Display
83 22 Jean-Philippe Lang
84 18 Mischa The Evil
h3. Theme
85 18 Mischa The Evil
86 18 Mischa The Evil
This option lets you choose a custom theme.
87 18 Mischa The Evil
Redmine is shipped with two additional themes besides the [[ThemeDefault|default]] theme:
88 1 Jean-Philippe Lang
* [[ThemeAlternate|alternate]], which mainly provides issue list colorization based on issues priority.
89 18 Mischa The Evil
* [[ThemeClassic|classic]], which is derived from the Redmine 0.5.1 design and brings a _classic_ look.
90 18 Mischa The Evil
91 18 Mischa The Evil
Screenshot of the [[ThemeAlternate|alternate]] theme:
92 18 Mischa The Evil
93 18 Mischa The Evil
!alternate_theme.png!
94 18 Mischa The Evil
95 18 Mischa The Evil
Themes are located in @public/themes/@. You can read more about [[Themes]].
96 18 Mischa The Evil
97 18 Mischa The Evil
h3. Default language
98 18 Mischa The Evil
99 1 Jean-Philippe Lang
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_
100 1 Jean-Philippe Lang
101 1 Jean-Philippe Lang
h3. Date format
102 1 Jean-Philippe Lang
103 18 Mischa The Evil
Lets you choose how dates are displayed:
104 18 Mischa The Evil
105 1 Jean-Philippe Lang
  * *Based on user's language*: dates will be displayed specifically for each user, according to the format defined for its language
106 1 Jean-Philippe Lang
  * *Other formats*: dates will always be displayed using the specified format
107 10 Jean-Philippe Lang
108 17 Thomas Lecavelier
_Default: Based on user's language_
109 17 Thomas Lecavelier
110 1 Jean-Philippe Lang
h3. Time format
111 3 Jean-Philippe Lang
112 1 Jean-Philippe Lang
Lets you choose how times are displayed:
113 1 Jean-Philippe Lang
114 1 Jean-Philippe Lang
  * *Based on user's language*: times will be displayed specifically for each user, according to the format defined for its language
115 1 Jean-Philippe Lang
  * *Other formats*: times will always be displayed using the specified format
116 1 Jean-Philippe Lang
117 1 Jean-Philippe Lang
_Default: Based on user's language_
118 1 Jean-Philippe Lang
119 1 Jean-Philippe Lang
h3. Users display format
120 1 Jean-Philippe Lang
121 1 Jean-Philippe Lang
Lets you choose how usernames are displayed. The following combinations are provided:
122 1 Jean-Philippe Lang
123 1 Jean-Philippe Lang
  * _Firstname_
124 1 Jean-Philippe Lang
  * _Firstname Surname_
125 1 Jean-Philippe Lang
  * _Surname Firstname_
126 1 Jean-Philippe Lang
  * _Surname, Firstname_
127 18 Mischa The Evil
  * _Username_
128 18 Mischa The Evil
129 18 Mischa The Evil
h3. Use Gravatar user icons
130 18 Mischa The Evil
131 18 Mischa The Evil
If enabled, users "Gravatars":http://en.gravatar.com/ (globally recognized avatar) will be displayed in several places.
132 18 Mischa The Evil
133 22 Jean-Philippe Lang
h3. Default Gravatar image
134 18 Mischa The Evil
135 22 Jean-Philippe Lang
The image to use for users who don't have a Gravatar.
136 18 Mischa The Evil
137 12 Jean-Philippe Lang
h2. Authentication
138 12 Jean-Philippe Lang
139 12 Jean-Philippe Lang
h3. Authentication required
140 12 Jean-Philippe Lang
141 41 Mischa The Evil
If this option is checked, no page of the application is accessible to anonymous users. Users must sign in to access the application. _Default: No_
142 12 Jean-Philippe Lang
143 12 Jean-Philippe Lang
h3. Autologin
144 12 Jean-Philippe Lang
145 12 Jean-Philippe Lang
This option let users use the auto-login feature. _Default: Disabled_
146 12 Jean-Philippe Lang
147 12 Jean-Philippe Lang
h3. Self-registration
148 12 Jean-Philippe Lang
149 12 Jean-Philippe Lang
This option lets you enable/disable new users self registration:
150 12 Jean-Philippe Lang
151 12 Jean-Philippe Lang
* *disabled*: users are not allowed to register
152 25 Michael Bishop
* *account activation by email*: new users receive an email containing a link used to activate their accounts (users must provide a valid email address).
153 1 Jean-Philippe Lang
* *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.
154 1 Jean-Philippe Lang
* *automatic account activation*: new users can log in as soon as they have registered.
155 1 Jean-Philippe Lang
156 21 Nick Fischer
h3. Minimum password length
157 18 Mischa The Evil
158 35 Mischa The Evil
Let's the admin decide on the minimum length of the chosen passwords.
159 18 Mischa The Evil
160 34 Mischa The Evil
_Default: 8_
161 1 Jean-Philippe Lang
162 18 Mischa The Evil
h3. Lost password
163 1 Jean-Philippe Lang
164 1 Jean-Philippe Lang
If this option is checked, lost password functionality is available. _Default: Yes_
165 1 Jean-Philippe Lang
166 18 Mischa The Evil
h3. Allow OpenID login and registration
167 18 Mischa The Evil
168 23 Jean-Philippe Lang
Provides the admin a way to disable OpenID logins and registrations.
169 1 Jean-Philippe Lang
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@.
170 1 Jean-Philippe Lang
171 37 Jan Niggemann (redmine.org team member)
h3. Session expiration
172 37 Jan Niggemann (redmine.org team member)
173 37 Jan Niggemann (redmine.org team member)
Session maximum lifetime: Lets the administrator set the maximum lifetime of the session
174 37 Jan Niggemann (redmine.org team member)
Session inactivity timeout: Lets the administrator specify after how many hors of inactivity the session times out.
175 37 Jan Niggemann (redmine.org team member)
%{color:red}Warning 1%: Changing these settings may expire the current sessions (including your own).
176 38 Daniel Felix
%{color:red}Warning 2%: Redmine uses the rails cookiestore for session management. We strongly advise you to set a maximum session lifetime. If you don't, it is theoretically possible that an attacker steals the session cookie and re-uses it.
177 37 Jan Niggemann (redmine.org team member)
178 1 Jean-Philippe Lang
h2. Projects
179 1 Jean-Philippe Lang
180 20 Mischa The Evil
h3. New projects are public by default
181 18 Mischa The Evil
182 1 Jean-Philippe Lang
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.
183 18 Mischa The Evil
184 18 Mischa The Evil
h3. Generate sequential project identifiers
185 18 Mischa The Evil
186 18 Mischa The Evil
This setting will let Redmine propose sequential project identifiers for you. This can still be manually changed only while creating the project, not afterward.
187 18 Mischa The Evil
188 18 Mischa The Evil
h3. Role given to a non-admin user who creates a project
189 18 Mischa The Evil
190 23 Jean-Philippe Lang
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).
191 18 Mischa The Evil
192 18 Mischa The Evil
h2. Issue tracking
193 18 Mischa The Evil
194 21 Nick Fischer
h3. Allow cross-project issue relations
195 18 Mischa The Evil
196 31 Jean-Baptiste Barth
If set to Yes, relations between issues from different projects can be created. _Default: No_
197 31 Jean-Baptiste Barth
198 32 Jean-Baptiste Barth
h3. Allow cross-project subtasks
199 32 Jean-Baptiste Barth
200 32 Jean-Baptiste Barth
Define some limits for subtasking. Definitions used are the same as version sharing, documented in [[RedmineProjectSettings#Versions]]. _Default: With project tree_
201 32 Jean-Baptiste Barth
202 32 Jean-Baptiste Barth
Options are:
203 32 Jean-Baptiste Barth
* @disabled@ : a parent task can only have subtasks in the same project.
204 32 Jean-Baptiste Barth
* @With all projects@ : a parent task can have subtasks in any other project.
205 32 Jean-Baptiste Barth
* @With project tree@ : a parent task can have subtasks in the same project, ancestor projects and all their descendants (e.g. also "sibling projects", "cousin projects", etc.).
206 32 Jean-Baptiste Barth
* @With project hierarchy@ : a parent task can have subtasks in the same project, subprojects, or ancestor projects.
207 32 Jean-Baptiste Barth
* @With subprojects@ : a parent task can only have subtasks in the same project or subprojects (not in parent projects or unrelated projects).
208 12 Jean-Philippe Lang
209 12 Jean-Philippe Lang
h3. Display subprojects issues on main projects by default
210 12 Jean-Philippe Lang
211 12 Jean-Philippe Lang
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_
212 12 Jean-Philippe Lang
213 26 Tharuka Pathirana
h3. Calculate the issue done ratio
214 26 Tharuka Pathirana
215 26 Tharuka Pathirana
Defines how the Issue Done Percentage is set.
216 26 Tharuka Pathirana
217 26 Tharuka Pathirana
* *Use the issue field* _(default)_: Users can manually set % done.
218 26 Tharuka Pathirana
* *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]].
219 26 Tharuka Pathirana
220 12 Jean-Philippe Lang
h3. Issues export limit
221 12 Jean-Philippe Lang
222 12 Jean-Philippe Lang
Maximum number of issues contained in CSV and PDF exports. _Default: 500_
223 12 Jean-Philippe Lang
224 12 Jean-Philippe Lang
h3. Default columns displayed on the issue list
225 12 Jean-Philippe Lang
226 12 Jean-Philippe Lang
This setting lets you define which columns are displayed on the issue lists by default.
227 12 Jean-Philippe Lang
Only custom fields that are marked as 'For all projects' can be selected here.
228 12 Jean-Philippe Lang
229 12 Jean-Philippe Lang
h2. Email notifications
230 12 Jean-Philippe Lang
231 12 Jean-Philippe Lang
h3. Emission mail address
232 12 Jean-Philippe Lang
233 12 Jean-Philippe Lang
Email address used in the "From" field of messages sent to users.
234 12 Jean-Philippe Lang
235 12 Jean-Philippe Lang
h3. Blind carbon copy recipients (bcc)
236 12 Jean-Philippe Lang
237 12 Jean-Philippe Lang
If set to true, email notification will be sent as Blind carbon copy. _Default: Yes_
238 12 Jean-Philippe Lang
239 12 Jean-Philippe Lang
h3. Plain text mail
240 12 Jean-Philippe Lang
241 12 Jean-Philippe Lang
If set to true, emails are sent in plain text only (no HTML).
242 15 Jean-Philippe Lang
243 15 Jean-Philippe Lang
h3. Emails footer
244 15 Jean-Philippe Lang
245 15 Jean-Philippe Lang
Here you can enter some text that will be appended to the emails sent by the application.
246 12 Jean-Philippe Lang
247 1 Jean-Philippe Lang
h2. Incoming emails
248 1 Jean-Philippe Lang
249 1 Jean-Philippe Lang
See for detailed instructions about these settings [[RedmineReceivingEmails]].
250 22 Jean-Philippe Lang
251 22 Jean-Philippe Lang
h3. Truncate emails after one of these lines
252 22 Jean-Philippe Lang
253 22 Jean-Philippe Lang
These setting can be used to remove signatures from incoming emails.
254 18 Mischa The Evil
255 18 Mischa The Evil
h3. Enable WS for incoming emails
256 18 Mischa The Evil
257 18 Mischa The Evil
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_
258 18 Mischa The Evil
259 18 Mischa The Evil
h3. API key
260 18 Mischa The Evil
261 18 Mischa The Evil
Within this setting you can enter a secret key used for the issue creation or comments via email feature.
262 18 Mischa The Evil
263 12 Jean-Philippe Lang
h2. Repositories
264 1 Jean-Philippe Lang
265 29 @ go2null
h3. Enabled SCM
266 29 @ go2null
267 29 @ go2null
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).
268 29 @ go2null
269 28 @ go2null
h3. Fetch commits automatically
270 1 Jean-Philippe Lang
271 3 Jean-Philippe Lang
If this option is activated, the application automatically retrieves the new revisions when a user consults the repository.
272 3 Jean-Philippe Lang
273 3 Jean-Philippe Lang
_Default: Yes_
274 14 Jean-Philippe Lang
275 3 Jean-Philippe Lang
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.
276 1 Jean-Philippe Lang
Example:
277 14 Jean-Philippe Lang
<pre>ruby script/runner "Repository.fetch_changesets" -e production</pre>
278 14 Jean-Philippe Lang
279 33 Alexander Menk
For Redmine 2.x:
280 33 Alexander Menk
281 33 Alexander Menk
<pre>ruby script/rails runner "Repository.fetch_changesets" -e production</pre>
282 33 Alexander Menk
283 42 Sebastian Paluch
For Redmine 3.x:
284 42 Sebastian Paluch
285 42 Sebastian Paluch
<pre>bin/rails runner "Repository.fetch_changesets" -e production</pre>
286 42 Sebastian Paluch
287 14 Jean-Philippe Lang
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.
288 36 Mischa The Evil
Here is a tutorial for doing so with git: http://www.barricane.com/remine-git-post-receive.html
289 3 Jean-Philippe Lang
290 18 Mischa The Evil
h3. Enable WS for repository management
291 18 Mischa The Evil
292 21 Nick Fischer
This option should be activated only if you installed the script for automatic SVN repository creation. _Default: No_
293 18 Mischa The Evil
294 8 Jean-Philippe Lang
h3. Repositories encodings
295 1 Jean-Philippe Lang
296 21 Nick Fischer
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.
297 8 Jean-Philippe Lang
When entering multiple encodings, the first valid encoding regarding the file content is used.
298 8 Jean-Philippe Lang
299 8 Jean-Philippe Lang
For French users, this option can be for example set to:
300 1 Jean-Philippe Lang
301 8 Jean-Philippe Lang
  UTF-8, ISO 8859-15, CP1252
302 1 Jean-Philippe Lang
303 1 Jean-Philippe Lang
For Japanese users:
304 1 Jean-Philippe Lang
305 8 Jean-Philippe Lang
  ISO-2022-JP, EUC-JP, UTF-8, SHIF_JIS, WINDOWS-31J
306 18 Mischa The Evil
307 18 Mischa The Evil
h3. Maximum number of revisions displayed on file log
308 18 Mischa The Evil
309 23 Jean-Philippe Lang
It provides a way to limit the amount of revisions which are retrieved from the SCM for a certain, browsed path.
310 4 Jean-Philippe Lang
311 12 Jean-Philippe Lang
h3. Referencing issues in commit messages
312 4 Jean-Philippe Lang
313 9 Jean-Philippe Lang
When fetched from the repositories, commit messages are scanned for referenced or fixed issue IDs.
314 9 Jean-Philippe Lang
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.
315 1 Jean-Philippe Lang
316 9 Jean-Philippe Lang
Default keywords are:
317 9 Jean-Philippe Lang
318 9 Jean-Philippe Lang
* for referencing issues: refs, references, IssueID
319 9 Jean-Philippe Lang
* for fixing issues: fixes, closes
320 9 Jean-Philippe Lang
321 9 Jean-Philippe Lang
There's no default status defined for fixed issue. You'll have to specify it if you want to enable auto closure of issues.
322 27 Larry Cai
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.
323 9 Jean-Philippe Lang
324 9 Jean-Philippe Lang
Example of a working commit message using default keywords:
325 9 Jean-Philippe Lang
326 9 Jean-Philippe Lang
  This commit refs #1, #2 and fixes #3
327 9 Jean-Philippe Lang
328 9 Jean-Philippe Lang
This message would reference issues 1 and 2 and automatically fix issue 3.
329 9 Jean-Philippe Lang
After a keyword issue IDs can be separated with a space, a comma or &.
330 30 Jean-Baptiste Barth
331 40 Ulf Renman
The keywords are caseinsensitive and at least one blankspace or colon is needed between the keyword and the first hash to produce 
332 40 Ulf Renman
a match. More examples that will produce the same result as the example above:<pre>
333 40 Ulf Renman
This commit refs:#1, #2 and fixes #3
334 40 Ulf Renman
This commit Refs  #1, #2 and fixes #3
335 40 Ulf Renman
This commit REFS: #1, #2 and fixes #3
336 40 Ulf Renman
</pre>
337 40 Ulf Renman
338 30 Jean-Baptiste Barth
h3. Enable time logging
339 30 Jean-Baptiste Barth
340 30 Jean-Baptiste Barth
Allows time logging directly from commit messages. This only makes sense if you activated the "Time tracking" module in said project. In this case, you can add special words in your commit message to indicate the time you spent on an issue.
341 30 Jean-Baptiste Barth
342 30 Jean-Baptiste Barth
The basic syntax for doing that is : @@<time>@, where time consists in a number of hours or minutes.
343 30 Jean-Baptiste Barth
344 30 Jean-Baptiste Barth
Here's a list of many valid commit messages that would work if you want to say you spent N hours on issue 1234: <pre>
345 30 Jean-Baptiste Barth
Implement feature #1234 @2
346 30 Jean-Baptiste Barth
347 30 Jean-Baptiste Barth
Implement feature #1234 @2h
348 30 Jean-Baptiste Barth
349 30 Jean-Baptiste Barth
Implement feature #1234 @2hours
350 30 Jean-Baptiste Barth
351 30 Jean-Baptiste Barth
Implement feature #1234 @15m
352 30 Jean-Baptiste Barth
353 30 Jean-Baptiste Barth
Implement feature #1234 @15min
354 30 Jean-Baptiste Barth
355 30 Jean-Baptiste Barth
Implement feature #1234 @3h15
356 30 Jean-Baptiste Barth
357 30 Jean-Baptiste Barth
Implement feature #1234 @3h15m
358 30 Jean-Baptiste Barth
359 30 Jean-Baptiste Barth
Implement feature #1234 @3:15
360 30 Jean-Baptiste Barth
361 30 Jean-Baptiste Barth
Implement feature #1234 @3.25
362 30 Jean-Baptiste Barth
363 30 Jean-Baptiste Barth
Implement feature #1234 @3.25h
364 30 Jean-Baptiste Barth
365 30 Jean-Baptiste Barth
Implement feature #1234 @3,25
366 30 Jean-Baptiste Barth
367 30 Jean-Baptiste Barth
Implement feature #1234 @3,25h
368 30 Jean-Baptiste Barth
</pre>
369 30 Jean-Baptiste Barth
370 30 Jean-Baptiste Barth
h3. Activity for logged time
371 30 Jean-Baptiste Barth
372 30 Jean-Baptiste Barth
This is the type of activity that should be used when detecting there's a log time in a commit message (see above).