You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-8Lines changed: 10 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -21,25 +21,27 @@ Meet the scripted Jira worklogging! Give it your worklogs in a CSV file (and you
21
21
## Configuration
22
22
23
23
The jwl.config file is a simple JSON structure. It can be placed in (and will be read by jwl in the priority order of)
24
-
- "current folder" (as in "where your shell's <code>%CD%</code> or <code>${PWD}</code> is at the moment")
25
-
- local application data (<code>%USERPROFILE%\AppData\Local</code>)
26
-
- roaming application data (<code>%USERPROFILE%\AppData\Roaming</code>)
27
-
- jwl's "installation" folder
24
+
- "current folder" (as in "where your shell's <code>%CD%</code> or <code>${PWD}</code> is at the moment")
25
+
- local application data (<code>%USERPROFILE%\AppData\Local</code>)
26
+
- roaming application data (<code>%USERPROFILE%\AppData\Roaming</code>)
27
+
- jwl's "installation" folder
28
28
29
29
As for the CLI worklogger binary, there are command-line options available as well. Any partial options supplied via CLI will override their respective jwl.config counterparts with the highest priority.
30
30
31
31
### "ServerClass" setting
32
32
33
33
Available values are:
34
-
- Vanilla
35
-
- TempoTimeSheets
36
-
- ICTime (not implemented yet)
34
+
- Vanilla
35
+
- TempoTimeSheets
36
+
- ICTime (not implemented yet)
37
37
38
38
## The input CSV structure
39
39
40
40
Five columns, data delimited (by default) by a colon:
41
41
- <code>Date</code> (string) - worklog day date (valid formats: <code>YYYY-MM-DD</code>, <code>YYYY/MM/DD</code>, <code>DD.MM.YYYY</code>, all with optional <code> HH:MI:SS</code> part)
42
42
- <code>IssueKey</code> (string) - Jira issue key (<code>SOMEPROJECT-1234</code> and the likes)
43
-
- <code>TempoWorklogType</code> (string) - Tempo Timesheets worklog type; values are checked against the available values from Jira server on each execution.
43
+
- <code>Activity</code> (string) - Tempo Timesheets worklog type or ICTime activity; values are remapped
44
44
- <code>TimeSpent</code> (string) - time to be logged for the Jira issue and the date (valid formats: <code>HH:MI</code>, <code>MI</code>, <code>HH h MI</code>, <code>HH h MI m</code>)
The <code>Activity</code> values are remapped via config <code>$.JiraServer.ActivityMap</code>. The mapping configuration depends on your Jira server+plugins configuration and is a subject of manual setup by yourself.
0 commit comments