App-TimeTracker-Command-Jira
view release on metacpan - search on metacpan
view release on metacpan or search on metacpan
Revision history for App-TimeTracker-Command-Jira
0.8 2019-05-09 16:24:11+02:00 Europe/Zurich
- Tidied up POD (Mohammad S Anwar)
0.7 2019-05-09 15:49:11+02:00 Europe/Zurich
- Make username and password Jira credentials optional and point to option where those can be stored encrypted via Config::Identity
0.6 2017-07-27 16:51:16+02:00 Europe/Zurich
- Branch selection based on (immutable) ticket number (maros)
- Load jira attribute only for commands that need it (maros)
0.5 2016-01-07 11:05:03+01:00 Europe/Vienna
- Allow to specifiy multiple starting states for transitioning to "Start Progress"
- Fixed github issue #1
### server \[REQUIRED\]
The URL of the Jira instance (without a trailing slash).
### username \[OPTIONAL\]
Username to connect with.
### password \[OPTIONAL\]
Password to connect with. Beware: This is stored in clear text! Better use authentication via `Config::Identity` via `JIRA::REST` where the credentials can be stored GPG encrypted.
### log\_time\_spent
If set, an entry will be created in the ticket's work log
# NEW COMMANDS ADDED TO THE DEFAULT ONES
none
# CHANGES TO DEFAULT COMMANDS
lib/App/TimeTracker/Command/Jira.pm view on Meta::CPAN
=head3 server [REQUIRED]
The URL of the Jira instance (without a trailing slash).
=head3 username [OPTIONAL]
Username to connect with.
=head3 password [OPTIONAL]
Password to connect with. Beware: This is stored in clear text! Better use authentication via C<Config::Identity> via C<JIRA::REST> where the credentials can be stored GPG encrypted.
=head3 log_time_spent
If set, an entry will be created in the ticket's work log
=head1 NEW COMMANDS ADDED TO THE DEFAULT ONES
none
=head1 CHANGES TO DEFAULT COMMANDS
view all matches for this distributionview release on metacpan - search on metacpan
( run in 0.526 second using v1.00-cache-2.02-grep-82fe00e-cpan-2c419f77a38b )