a26683e01d
update all usage of user.name to user.accountId for privacy migration:
...
https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/
2020-02-23 23:59:39 -08:00
d002d7fe74
allow issues on command line to automatically prefix with project when defined
2019-12-01 16:29:35 -08:00
27f57b2bbe
Switch over to using github.com/go-jira/jira, from gopkg.in
...
There should be no reason to use gopkg.in versioned imports now that
we're using go modules. I think, IANAE.
gopkg.in kind of gets in the way of modules, as it only pulls over
tagged releases from github.com -- this then means that you need to use
go modules 'replace' syntax in the go.mod to use a non-versioned commit
or branch. This is feasible, but kind of ugly.
go modules defaults to pulling the latest version, so the default
behavior is the same as when pulling go-jira.v1 from gopkg.in.
2019-09-14 21:31:11 -07:00
31c113d1ba
all: unindent some code
2019-05-28 11:01:51 +01:00
9b9186f7d4
start making staticcheck happier
2019-05-27 10:49:15 +01:00
9146346e2f
[ #163 ] fix url path join logic
2018-04-15 16:56:09 -07:00
9597f9b56f
fix transition comman
2017-10-28 14:46:50 -07:00
c9b5054cde
fix default values to load after parsing configs
2017-10-28 14:23:27 -07:00
4ed8edbd19
Add --resolution option
2017-10-13 12:22:12 -06:00
c4be59cae3
[ #45 ] automatically add comment to issue even if transition does not support comment updates during transtion
2017-09-06 21:28:57 -07:00
c226077320
add --quiet global option
2017-09-04 18:12:32 -07:00
c0358eb67c
refactor to allow for --insecure and --unixproxy arguments
2017-09-04 17:53:01 -07:00
2638396606
add resolution to dup'd issues when necessary
2017-09-03 00:38:37 -07:00
979da1f3a5
refactor for GlobalOptions and CommonOptions
2017-09-02 14:05:27 -07:00
0a5510b231
move commands from jiracli package to jiracmd package
2017-09-02 09:14:54 -07:00
Cory Bennett