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
{{ message }}
This repository has been archived by the owner on Jun 9, 2021. It is now read-only.
A user will be able to log hours by providing ticket ids and optionally durations by using a specific syntax.
He can also specify a date for hours to be logged in different date than the current one (today).
ISSUES_WITH_DURATIONS log argument (Required): It's a string which contains comma-separated issues with optional durations and start times. To clarify things a little bit, lets say a user enters the following command: jira-logwork log ABC-123=10:00|1h30m,ERS-52=1h,ESS-312,EF-4123 --date 23/06/2020
The parser will execute the following steps:
Splits the ISSUES_WITH_DURATIONS string to separate issues and get their options (if any). It uses comma separator(,) for issues and pipe separator(|) for options. In our case it will create the following table:
jira_id
start_time
duration
adjustment_mode
converted_duration
ABC-123
10:00
1h30m
fixed
ERS-52
1h
fixed
ESS-312
auto
EF-4123
auto
Fills the missing values by making conversions. The final table will be the following:
jira_id
start_time
duration
adjustment_mode
converted_duration
ABC-123
10:00
1h30m
fixed
5400
ERS-52
11:30
1h
fixed
3600
ESS-312
12:30
2h45m
auto
9900
EF-4123
15:15
2h45m
auto
9900
TOTAL
-
8h
-
28800
It takes into account the configuration params given in configuration step. In this example, they are the following: shift_start: 10:00, shift_end: 18:00
The text was updated successfully, but these errors were encountered:
Description
A user will be able to log hours by providing ticket ids and optionally durations by using a specific syntax.
He can also specify a date for hours to be logged in different date than the current one (today).
Command
bin/jira-logwork log [ISSUES_WITH_DURATIONS] --date [DATE]
Arguments
ISSUES_WITH_DURATIONS log argument (Required): It's a string which contains comma-separated issues with optional durations and start times. To clarify things a little bit, lets say a user enters the following command:
jira-logwork log ABC-123=10:00|1h30m,ERS-52=1h,ESS-312,EF-4123 --date 23/06/2020
The parser will execute the following steps:
It takes into account the configuration params given in configuration step. In this example, they are the following:
shift_start: 10:00, shift_end: 18:00
The text was updated successfully, but these errors were encountered: